On 18/07/2012, at 5:12 PM, Quincey Morris wrote:
> It would seem that floating panels ought to follow the #2 and #3 rule. It's
> not clear that "window activation state" is meaningless. A user should be
> able to see, for example, whether the up and down arrows move the selection
> in the sour
On 18.07.2012, at 09:12, Quincey Morris wrote:
> There are 3 states for enabled controls**, not two:
>
> 1. In an inactive window (Snow Leopard+ at least -- I think the appearance
> was different in Leopard), controls are colorless with a lighter shade of
> gray textured background (just like th
On 18.07.2012, at 06:27, Graham Cox wrote:
> I'd like to know if there is a supported way to do this. It seems a bit crazy
> that floating panels even bother modulating the active state of controls when
> they are floating and are *always* effectively active, and it looks better
> and is more us
On Jul 17, 2012, at 21:44 , Graham Cox wrote:
> The particular thing that's bothering me the most is that I have a
> source-list outline view in my floating palette, and it responds to the
> window activation state even though for the floating panel it's meaningless.
> I'd rather it didn't and
On 18/07/2012, at 2:27 PM, Graham Cox wrote:
> This no longer seems to work since some versions ago
On further investigation, it is still being called (as of Lion). But it's still
an undocumented hack.
The particular thing that's bothering me the most is that I have a source-list
outline vie
My app has floating palettes that generally set [NSPanel
setBecomesKeyOnlyIfNeeded:YES]; Most of the time these palettes are therefore
inactive, and yet provide a large number of useful controls that work as
expected when operated. Problem is, a lot of these controls show the inactive
state bec
