Re: Window levels - is this safe?

FROM : Ricky Sharp
DATE : Wed Jul 26 20:07:33 2006

On Wednesday, July 26, 2006, at 08:13AM, Keith Blount <<email_removed>> wrote:

>Many thanks for your reply - much appreciated. I think
>your suggestion may well be the way to go. Full screen
>in my app is supposed to be a "no distractions" mode,
>so blocking application switching and Expose may
>actually be a bonus rather than a problem.
>
>My only problem now is that I do not have access to a
>dual- or multi-screen set up for the time being, so
>although I can have a go at coding the blanking
>screens, I'll have to rely on my beta testers to tell
>me whether or not it works. :) My plan is to create
>the blanking windows in the -showWindow: code of my
>main window, and then add the main window as s child,
>and get rid of all the blanking windows in the -close
>method. I can then monitor for
>NSApplicationDidChangeScreenParametersNotification and
>update the blanking windows as necessary. Does that
>sound about right?


That does sound good.  For my app, I set up all windows in applicationDidFinishLaunching and then tear them down in applicationWillTerminate.  But your approach should yield them same results.

I don't currently handle updates via that screen changed notification.  Hmm, I guess I'll do that :)

Oh, one thing to point out.  My app, although full-screen, can switch out to a web browser since one of my "screens" contains a hyperlink.  I set up my windows to autohide when not frontmost, so my app effectively hides itself when this is done.  I suppose users could, at that time, make changes to displays such that switching back to my app would cause grief since blanking windows would not be positioned or sized correctly.

--
Rick Sharp
Instant Interactive(tm)