🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.programmer
Article #1904

Re: Making a window... not a window.

#1904
From: Sam Streeper
Date: Tue, 24 Nov 1992 01:51
22 lines
1328 bytes
matthews@oberon.umd.edu (Mike Matthews) writes:
> How in blazes are you supposed to make a window that can not be moved?  I
> know you have to use the initContext:... stuff (i.e. not use IB's palettes).
> I tried passing a style of NX_PLAINSTYLE to the window but the doggone title
> bar was logically there.

You were probably on the right track.  If memory serves me a window with a null  
button mask has no title/move bar.  The following code seems to do what you  
want:

	window = [[Window alloc] initContent:&r style:NX_PLAINSTYLE
			backing:NX_BUFFERED buttonMask:0 defer:NO];

I think plain windows, tastefully used, don't have to violate anybody's idea of  
how a NeXTstep app ought to work.  They are very useful for all kinds of custom  
UI and I for one like to see intuitive UI objects other than those found in IB.

-sam

--
Opinions expressed herein are not those of my employer.  They're not even
mine.  They're probably wrong besides.  How did they get in here, anyway?
Technical Details
Message-ID: <5931@rosie.NeXT.COM>
Path: arc1-ca.pugleaf.net!sparky!uunet!rosie!NeXT.com
References: <17039@umd5.umd.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!rosie!NeXT.com
From: sam_s@NeXT.com (Sam Streeper)
Newsgroups: comp.sys.next.programmer
Subject: Re: Making a window... not a window.
Message-ID: <5931@rosie.NeXT.COM>
Date: 24 Nov 92 01:51:58 GMT
References: <17039@umd5.umd.edu>
Sender: news@NeXT.COM
Reply-To: sam_s@NeXT.com
Lines: 22