Re: classic floating window behavior?

• Subject: Re: classic floating window behavior?
• From: m <email@hidden>
• Date: Wed, 31 Mar 2004 13:36:50 -0800

At 13:05 Uhr -0800 30.03.2004, m wrote:

SetWindowClass((WindowRef)[mFloater windowRef], kFloatingWindowClass);

(mFloater in this case is a pre-existing NSPanel instantiated from the Nib file.) In this instance, I got a floating window that still floats above all app windows.

Okay, then it looks like I simply remembered something of the way it worked in OS 9. This definitely used to work this way in Carbon, but I guess they don't have any application-specific layers in OS X anymore. I see one more venue to investigate:

Use setLevel: to move your window into the document layer, and use a category to replace orderFront: and any other window-order-changing methods with a method that does the same as orderFront: (never done this, but I heard it is messy because you need to get the IMP of the original method to be able to call it and only *then* load the category, e.g. from a bundle) and afterwards sends all your floaters an orderFront: as well.

• Prev by Date: Re: [OT] Retain count riddle
• Next by Date: Wanted Gradient Fill for NSBezierPath
• Previous by thread: Re: classic floating window behavior?
• Next by thread: Re: classic floating window behavior?
• Index(es):
  • Date
  • Thread