Re: NSWindow order back and stay, dammit!
Re: NSWindow order back and stay, dammit!
- Subject: Re: NSWindow order back and stay, dammit!
- From: Sam Goldman <email@hidden>
- Date: Sat, 1 Sep 2001 15:55:55 -0700
That solves my first problem (thank you), but I am not sure about the
second. I'll have to do more development, but it seems like my second
problem will still be a problem.
--------- second problem ---------
Another problem: I want it to run completely separate from the Finder,
so any applications that open from it don't show in the Finder and any
applications in the Finder don't show in it.
------------------------------------------
-sam
On Saturday, September 1, 2001, at 03:06 PM, Finlay Dobbie wrote:
>
You can set its level to CGWindowLevelForKey(kCGDesktopWindowLevelKey),
>
would that work?
>
>
-- Finlay
>
>
On Saturday, September 1, 2001, at 11:00 pm, email@hidden wrote:
>
>
> I have an secret project that takes over the whole screen (hint: it's
>
> a desktop) and I want to open inter/intra-application windows over it.
>
> The user needs to be able to click on it and get contextual menus, but
>
> it should stay behind all other windows. The way I have it working
>
> right now is most likely not correct. I use the shielding window level
>
> get the display, then use it again to open other windows. It works
>
> except that when I click on the full screen window, my new window goes
>
> behind it.
>
>
>
> Another problem: I want it to run completely separate from the Finder,
>
> so any applications that open from it don't show in the Finder and any
>
> applications in the Finder don't show in it.
>
>
>
> I want it to run along side (and on top of) the Finder, not replace
>
> it. Any insights on things relevant would be great, especially if they
>
> are related to these problems.
>
_______________________________________________
>
cocoa-dev mailing list
>
email@hidden
>
http://www.lists.apple.com/mailman/listinfo/cocoa-dev