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 163190 - Tools lose their settings after a menu action
Tools lose their settings after a menu action
Status: RESOLVED DUPLICATE of bug 163163
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.4.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-01-07 00:53 UTC by Michael J. Redd
Modified: 2005-01-31 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael J. Redd 2005-01-07 00:53:10 UTC
This is a bug that was originally posted in the GIMP bug repository, but after
some thinking and throwing possibilities back and forth with GIMP developers, I
believe this could be more of a GTK/wintab issue.

For reference and details, please refer to the original GIMP bug report, which
can be found at:
http://bugzilla.gnome.org/show_bug.cgi?id=163163

Here's a summary:

"When using the Win32 version of GIMP 2.2.1 with GTK version 2.4.14 and a Wacom
graphics tablet, executing a menu command causes the tools to lose their
settings and revert back to GIMP's startup defaults. For example, I set my
stylus to use the Brush tool, change the brush size to Fuzzy size 3,
set pressure options, and change the color to blue. After I save my work via
File>Save, the Brush tool's options revert back to the default size, no pressure
sensitivity, and black."

It did seem like a problem specific to GIMP at first, but when I realized the
bug didn't reproduce on a Linux system or when using a non-wintab device, it
started to sound like a GTK/wintab issue.

Again, please see the original GIMP bug report for more details.
Comment 1 Robert Ögren 2005-01-07 16:32:09 UTC
Thank you for bringing this to our attention. I have added a comment to bug
#163163. This bug (163190) should probably be closed and 163163 reassigned to
GTK+ instead, but don't worry about that. We'll handle that when necessary.
Comment 2 Robert Ögren 2005-01-31 17:24:00 UTC
Closing this bug as bug #163163 was reassigned to GTK+.

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