From kde-core-devel Thu Nov 30 21:35:13 2006 From: Matthew Woehlke Date: Thu, 30 Nov 2006 21:35:13 +0000 To: kde-core-devel Subject: Re: RFC: Making focus information visible for panes Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=116496380204005 Matthew Woehlke wrote: > All that said, there is still another major problem: you don't have one > QStyle instance per widget, you have one per *container* (and I did > /verify/ that), and, except in cases (e.g. kuiviewer) where you > intentionally create more than one container, I think that generally > translates into one instance /per application/. IOW, changing the > palette changes it for ALL widgets, so you would have to be REALLY, > really careful to only draw the control with keyboard focus with the > altered palette. (WCTS) I'm not sure that's even possible, in which case > this entire discussion is moot, because doing this /outside/ the style > just plain won't work. Hmm, ok I'm not sure if that's true or not. I was just noticing (again) that KDevelop already does this sort of palette hacking (and /on highlight colors/, no less). I'm not sure if it is forcing a separate style instance or not (if it isn't, it should be for the previously mentioned reasons). However, the reason I notice is because KDevelop doing this already causes problems. The issue remains that you are circumventing behavior in the style, which can cause visual glitches /in the style/. In fact, I'm going to go report this to KDevelop now. -- Matthew "Lost a planet, Obi Wan has? How embarassing..." -- Yoda (Star Wars II: Attack of the Clones)