Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!pepper!cmcmanis From: cmcmanis%pepper@Sun.COM (Chuck McManis) Newsgroups: comp.sys.amiga.tech Subject: Re: IDCMP ports Message-ID: <50350@sun.uucp> Date: 21 Apr 88 17:39:00 GMT References: <2336@mit-amt.MEDIA.MIT.EDU> Sender: news@sun.uucp Reply-To: cmcmanis@sun.UUCP (Chuck McManis) Distribution: na Organization: Sun Microsystems, Mountain View Lines: 39 Keywords: screens windows [Net delays are curious things...] In article <2336@mit-amt.MEDIA.MIT.EDU> (Darren L. Leigh) writes: >This is probably a dumb question and so should probably be answered by >mail, but: Actually it is a pretty common stumbling block for beginners. I sometimes wonder how fast new people join this group and need to see this information again. >If I have an application that has created a custom screen and I don't >want to open any windows, how do I get an IDCMP port between me and >Intuition? All the documentation talks about windows and I don't see >a way to do it otherwise. I just want some mouse moves and gadget >information without cluttering up the world with windows. The answer is, you open window the same size as the screen and give it the attributes BORDERLESS+BACKDROP. This window will be 'invisible' because it will be the same color as the screen. (color 0). As it turns out, the bitmap data will be the same too, that is you can render through the screen's RastPort (MyScreen -> RastPort) or the windows RastPort (MyWindow->RPort) and the data will appear at about the same place. I say about because if the window is not at coordinate 0,0 on the screen then the coordinates between the two RastPorts will be off by the top left edge of the screen. When I use this configuration I leave the window on line 1 rather than line 0, that way I can still drag the screen by selecting it's drag bar. The vestigal windows on the workbench are usually the result of a friendly C compiler trying to make sure you have a StdOut and StdIn window to play with. If this isn't open and your program does a printf() then Mr. Guru to the rescue. Now in other cases there is no easy way to tell your application to quit so the small window on the workbench may be nothing more than a remote close gadget that you monitor to tell you when to stop. RoboCity which double buffers the display does this. --Chuck McManis uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com These opinions are my own and no one elses, but you knew that didn't you.