Re: Locking Access to Windows
Re: Locking Access to Windows
- Subject: Re: Locking Access to Windows
- From: John Stiles <email@hidden>
- Date: Mon, 9 May 2005 18:30:54 -0700
On May 9, 2005, at 6:25 PM, Matt Neuburg wrote:
On Mon, 9 May 2005 16:07:51 -0500, Kevin Cox <email@hidden>
said:
I am trying to find in the Cocoa docs how to lock an application
window
from input when a child window is in place. For instance, you click a
button in the main app window and another window is launched. How do
you lock the main app window from input until the other window is
closed?
If this is really necessary you could disable all the interface items
in the
main app window. But you're describing a situation that should, in
effect,
be impossible. If opening window 2 means the user should not interact
with
window 1 then why not just hide window 1? Or, as already suggested,
make
window 2 a sheet of window 1, which disables window 1 automatically. m.
In general, Mac OS does not treat windows as "parent" and "child." Each
window stands alone.
Users don't typically intuit the parent<->child relationship anyway.
Windows only does it this way because their code treats the window
hierarchy as a big tree, i.e. controls are just implemented as HWNDs
inside other HWNDs, and this coding style leaked out into the
presentation of the user interface. I'm not impressed :) Mac OS
philosophy should be to design the user interface first, and then worry
about how to implement that.
As the previous poster suggests, if you want a window to be a child of
a parent window, perhaps you really want a sheet.
If you want a window that isn't attached to any other window but
overrides all the other windows, perhaps you want a modal window.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden