>> OK, so it can be fixed by a custom theme, but not just by a custom RC >> file, and therefore still remains a problem for almost all apps. I >> don't of many (any?) apps that ship with a custom theme, whereas quite >> a few do use their own RC file. The design of those files still >> implies that prelight is a separate state from active/normal, rather >> than a flag set "on top" of those states. > >"Touchscreen" really isn't an application issue. If an application=20 >changed the prelight behavior of GTK+ without being part of an=20 >isolated system, that would be quite broken. i think this is unrealistic. for ardour, we firmly believe that the default themes that exist for GTK+ are pretty unusable because they do not use color to provide easily locatable visual information. when you want to see easily which tracks are record-enabled and soloed but not muted, a set of identically colored (and typically dirty gray) buttons amidst hundreds of others just doesn't work. ergo, color to indicate widget state is critical, and that's precisely where PRELIGHT interferes. does this mean that gcombust should not use prelight, or that other GTK apps should not? of course not. ergo, it *can* be an application issue. --p _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
