After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705175 - selected color reverts back to previous color when using 2 pointer devices
selected color reverts back to previous color when using 2 pointer devices
Status: RESOLVED DUPLICATE of bug 667862
Product: GIMP
Classification: Other
Component: User Interface
2.8.6
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-07-30 21:50 UTC by dirtslayer
Modified: 2013-08-02 14:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dirtslayer 2013-07-30 21:50:35 UTC
i use both a mouse and a tablet. i have dual monitors as well. i put the controls in one monitor and the drawing in the other monitor. i use xsetwacom to restrict my tablet to the drawing monitor. so to change colors i use the mouse since the tablet pen will not reach the monitor with the controls. when i select a color with the mouse, then switch back to the tablet to draw the color reverts back to the previous color. the only way for me to keep the color i want is to put the color dialog in the same monitor as the drawing and use the tablet to select the color
Comment 1 dirtslayer 2013-07-30 21:54:51 UTC
the fact that i have dual monitors is irrelevant, that is just the reason its important, you can duplicate this bug with 1 monitor and 2 pointing devices.
Comment 2 Michael Schumacher 2013-07-31 14:02:38 UTC
That's a feature - usually, people want each device to have it's own settings, up to different tools.

Not sure if we already have an enhancement request for sharing tools and their options across different devices, I can't find one right now.
Comment 3 Michael Natterer 2013-08-02 14:41:30 UTC
This is essentially the same request as bug 667862, only for a different
reason, resolving as duplicate.

*** This bug has been marked as a duplicate of bug 667862 ***