Color Picker popup in secondary monitor immediately closes while still hovering #85737

New Issue

Duarte Farrajota Ramos · 2021-02-17T12:56:12+01:00

2021-02-17 12:56:12 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Quadro P4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.39
Also tested on a system with dual NVIDIA RTX 3090 with same effect
Dual monitor setup

Blender Version
Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-02-16 12:47, hash: c13754e647
Worked: 2.91.2 5be9ef4177

Short description of error
The color picker popup in secondary monitor closes immediately after adjusting a value while still hovering.

Exact steps for others to reproduce the error
Under a fresh default installation of Blender 2.92 Beta the color picker popup loses focus and closes when moving the mouse, after adjusting any property (from the color wheel or individual values) while still hovering, without the cursor leaving the popup.

Under the default startup file go to the properties window in any color picker, like say in the default cube material
Click diffuse color and it should work reliably
Now move the window to the second monitor so the color picker is shown in the other display
If you now click diffuse color and adjust any value (from the color wheel or individual values) the popup closes) by click or drag while still hovering, without the cursor ever leaving the popup area.

Moving the window back to the original display reverts to the correct behavior

This was tested with various 2.92 betas in the last few days, on two different systems, both with two monitors running Windows 10 64bits, and happens most reliably on the secondary monitor, although it can be less frequently reproduced on the main as well.
I tested on different Mainand Secondarywindows and in different editors (originally it happened in the Shader Node Editor). Some times the issue "propagated" to the main screen, when dragging the window back, and one had to close the editor (say collapse the Properties Window to an adjacent Outliner) and reopen it to revert back to the original intended behavior.

The following capture was done at the edge between two monitors, the main screen to the left half, and the secondary display on the right. When I move the Blender window I'm actually dragging it so the color picker transitions between displays.

blendercolorpicker.mp4

system-info.txt

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: Quadro P4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.39 Also tested on a system with dual NVIDIA RTX 3090 with same effect Dual monitor setup **Blender Version** Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-02-16 12:47, hash: `c13754e647` Worked: 2.91.2 5be9ef417703 **Short description of error** The color picker popup in secondary monitor closes immediately after adjusting a value while still hovering. **Exact steps for others to reproduce the error** Under a fresh default installation of Blender 2.92 Beta the color picker popup loses focus and closes when moving the mouse, after adjusting any property (from the color wheel or individual values) while still hovering, without the cursor leaving the popup. - Under the default startup file go to the properties window in any color picker, like say in the default cube material - Click diffuse color and it should work reliably - Now move the window to the second monitor so the color picker is shown in the other display - If you now click diffuse color and adjust any value (from the color wheel or individual values) the popup closes) by click or drag while still hovering, without the cursor ever leaving the popup area. # Moving the window back to the original display reverts to the correct behavior This was tested with various 2.92 betas in the last few days, on two different systems, both with two monitors running Windows 10 64bits, and happens most reliably on the secondary monitor, although it can be less frequently reproduced on the main as well. I tested on different *Main*and *Secondary*windows and in different editors (originally it happened in the *Shader Node Editor*). Some times the issue "propagated" to the main screen, when dragging the window back, and one had to close the editor (say collapse the Properties Window to an adjacent *Outliner*) and reopen it to revert back to the original intended behavior. The following capture was done at the edge between two monitors, the main screen to the left half, and the secondary display on the right. When I move the Blender window I'm actually dragging it so the color picker transitions between displays. [blendercolorpicker.mp4](https://archive.blender.org/developer/F9811960/blendercolorpicker.mp4) [system-info.txt](https://archive.blender.org/developer/F9811963/system-info.txt)

Duarte Farrajota Ramos commented

2021-02-17 12:56:12 +01:00

Added subscriber: @DuarteRamos

Ermins Ermanis commented

2021-02-17 13:10:42 +01:00

Added subscriber: @erminos

Ermins Ermanis commented

2021-02-17 13:10:42 +01:00

Could be the same - #84701. It was fixed just this morning, and commit ab21009842 should be available for download later, maybe tomorrow.

Could be the same - #84701. It was fixed just this morning, and commit ab210098424b should be available for download later, maybe tomorrow.

Duarte Farrajota Ramos commented

2021-02-17 13:23:47 +01:00

In #85737#1114155, @erminos wrote:
Could be the same - #84701. It was fixed just this morning, and commit ab21009842 should be available for download later, maybe tomorrow.

I saw that commit too and it sounded familiar, was hoping to see the issue fixed with it but it did not.
It stated being submitted at Wed, Feb 17, 01:45, the build I just tested with says it is from February 17, 00:08:28- c13754e647 on the buildbot which seems after that.
Unless there's some timezone shenanigans in those timestamps, there is some delay, or the commit somehow didn't actually make it in time for compilation, I'd expect it to be included unless I'm missing something else.

I'll test again in a few hours when there's a new buildavailable to make sure and report here.

> In #85737#1114155, @erminos wrote: > Could be the same - #84701. It was fixed just this morning, and commit ab210098424b should be available for download later, maybe tomorrow. I saw that commit too and it sounded familiar, was hoping to see the issue fixed with it but it did not. It stated being submitted at Wed, Feb 17, 01:45, the build I just tested with says it is from February 17, 00:08:28- c13754e6475e on the [buildbot](https://builder.blender.org/download) which seems after that. Unless there's some timezone shenanigans in those timestamps, there is some delay, or the commit somehow didn't actually make it in time for compilation, I'd expect it to be included unless I'm missing something else. I'll test again in a few hours when there's a new buildavailable to make sure and report here.

Falk David commented

2021-02-17 14:00:16 +01:00

Added subscriber: @filedescriptor

Falk David commented

2021-02-17 14:00:16 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Falk David closed this issue

2021-02-17 14:00:16 +01:00

Falk David commented

2021-02-17 14:00:16 +01:00

Feb 17, 00:08 AM is clearly before Feb 17, 2:45 AM which is when this was committed. Since I can't reproduce this with my local build, I assume this is fixed. Feel free to reopen if the problem persists once the buildbot build is up-to-date.

Duarte Farrajota Ramos commented

2021-02-17 14:25:45 +01:00

In #85737#1114193, @filedescriptor wrote:
Feb 17, 00:08 AM is clearly before Feb 17, 2:45 AM

Apologies, I misinterpreted the timestamp, I read it as 8AM, not 00h08. I'll reopen if needed, sorry for the noise.

> In #85737#1114193, @filedescriptor wrote: > Feb 17, 00:08 AM is clearly before Feb 17, 2:45 AM Apologies, I misinterpreted the timestamp, I read it as 8AM, not 00h08. I'll reopen if needed, sorry for the noise.

Falk David commented

2021-02-17 16:41:01 +01:00

Wasn't meant to sound condescending. No worries :)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Color Picker popup in secondary monitor immediately closes while still hovering #85737

Moving the window back to the original display reverts to the correct behavior