Re: NSRunAlertPanel

[Andreas Höschler]

Hello Fred,

> > > Look in NSAlert.m
> > > Perhaps GSAlertPanel should call [self setFloatingPanel: YES] in its
> > > initialisation?
> >
> > Thanks!
> >
> > However, this did not make a difference! I checked the window levels. 
> > My
> > main window has NSNormalWindowLevel, the NSRunAlertPanel has
> > NSFloatingWindowLevel. Normally it should always be above the main 
> > win,
> > but it is not. Could this be window manager related? I am using 
> > sawfish
> > on the debian system! May be sawfish is so simple that it does not
> > support different window levels.
>
> That is a bit strange, due to the code in [NSApplication
> beginModalSessionForWindow:] the panel should be changed to
> NSModalPanelWindowLevel during the loop. Could you please re-check 
> this?

OK, my log gave the level of the panel immedaitely before the runModel 
call, so...

> But most likely your actual problem is the window manager. You will 
> need
> to find out what special settings are needed for it. Then we may add
> them to setwindowlevel: in back.

Usually we use Window Maker (under Solaris). There we have never seen 
this problem. Under Dbian we use sawfish for its simplicty (application 
in kiosk mode). That's what makes me thinking that thi sis window 
manager related. But I have no idea whether the bug is in sawfish or in 
GNUstep. What special settings do you mean?

Is anybody (except us) actually using sawfish together with GNUstep and 
has observed something similar?

Thanks,

  Andreas