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 51747 - Rethink GtkStateType
Rethink GtkStateType
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
1.3.x
Other All
: Normal enhancement
: 3.0
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 51731 347771
 
 
Reported: 2001-03-06 01:24 UTC by Owen Taylor
Modified: 2011-01-04 13:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Owen Taylor 2001-03-06 01:24:30 UTC 
(http://mail.gnome.org/archives/gtk-devel-list/2001-March/msg00125.html)

A number of problems can be identified with the current GtkStateType
enumeration. 
 
 * The color setup in RC files is very non-intuitive
 * State types are misused for things like the scrollbar trough
 * The states sometimes should be combined.
 * gtk_paint_* implementatiosn have great number of hacks involving
   special detail strings
 * It's hard to extend the current system to include an inactive state

The proposal is to factor state into "the type of thing being drawn"
(normal, selected, depressed, base) and "the event state" (normal,
prelight, inactive, sensitive)
Comment 1 Owen Taylor 2001-03-06 01:32:50 UTC 
(Putting on 2.0 API, but high punt probability)
Comment 2 Owen Taylor 2001-06-05 19:41:30 UTC 
Going to have to wait for GTK+-3, most likely. :-(
Comment 3 Javier Jardón (IRC: jjardon) 2011-01-04 13:48:46 UTC 
This was solved in GTK+3 with the new GtkStyleContext and GtkStateFlags, I think