Re: classic floating window behavior?
Re: classic floating window behavior?
- Subject: Re: classic floating window behavior?
- From: m <email@hidden>
- Date: Mon, 29 Mar 2004 18:10:25 -0800
On Mar 29, 2004, at 5:50 PM, M. Uli Kusterer wrote:
At 13:15 Uhr -0800 29.03.2004, m wrote:
Have you tried setWindowLevel or setWindowLayer or whatever the
method on NSWindow is called? You can pass in any CGWindowLevel, not
just the ones defined in NSWindow.h
Yes. The problem is not the particular level a window lives in. It's
that in Mac OS X, there is no longer a the concept of an application
layer; windows from multiple apps can be interleaved. A consequence
of this is that the "floating" layer has to be a global floating
layer.
Definitely not. Carbon has kFloatingWindowClass and
kUtilityWindowClass. The latter works like Cocoa's system-wide
floaters, the former stays in front of the frontmost document window
of your app.
Using either kFloatingWindowClass or kUtilityWindowClass as an argument
for setLevel results in the identical behavior.
_murat
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.