Re: Aqua Interface Guidelines & Close Window location ?
Re: Aqua Interface Guidelines & Close Window location ?
- Subject: Re: Aqua Interface Guidelines & Close Window location ?
- From: Ondra Cada <email@hidden>
- Date: Thu, 20 Sep 2001 13:50:05 +0200
Rosyna and all,
>
>>>>> Ondra Cada (OC) wrote at Thu, 20 Sep 2001 13:24:27 +0200:
R>> Not sure if you noticed, but utility windows should never get focus
R>> (and never do)
I guess this might need an explanation. Actually, there are two *orthogonal*
properties of a window:
(i) is floating / is not floating
A floating window is in another tier than the normal windows. Therefore, it
can never be obscured by a normal window. (It can be obscured by another
floating window from the same or more-front tier, but that's unimportant
now.)
(ii) can become key window (=become first responder, =get focus) / can not
Whilst a standard window would become first responder whenever clicked, the
code can prevent that, either to reduce the ways how the window can become
FR, or to prevent becoming FR at all.
Now, all four combinations are possible. The limits are conventions:
- document window should never prevent becoming FR and should never float
(unless there are *EXTREMELY* strong reasons to do so);
- panels should prevent becoming FR unless needed (that means that a panel
should become FR only if there is an editable widget inside it, and _that_
widget is to become FR. Also that means that a panel without any editable
view should never become FR.);
- as for floating, the opinions differ; therefore panels should have a
widget which would allow _user_ to select whether the particular panel should
float or not. I, for one, would never make Font panel float; _sometimes_
though I would do that with Finder inspector.
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc