Path: utzoo!attcan!uunet!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Finding Screens
Message-ID: <14480@cbmvax.commodore.com>
Date: 17 Sep 90 15:35:11 GMT
References: <26f437ee-918comp.sys.amiga.tech@tronsbox.xei.com>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore, West Chester, PA
Lines: 33

In article <26f437ee-918comp.sys.amiga.tech@tronsbox.xei.com> tron1@tronsbox.xei.com (HIM) writes:
>
>
>But I would like most of it to be in the form of expandable modules so I
>need to write a program that will...
>
>     1) Find the screen of the master program.
>
>     2) Open a window on that screen.
>
>I will use message ports to have the client tell the master that there is a
>window there to avoid confusion, but inso far as FINDING the screen goes...
>
>Should I have the client wak the Screen structure list starting at the
>workbench screen ? (I assume this will break in 2.0) or should it get the
>pointer as a message from the host ????

No.  Do not walk the screen structure.  Two cooperating programs should
anyways have a method of talking to each other about application specific
things, so make this just another piece of information.  It seems to
me that initial rendezvous between two cooperating things should be
done by finding a "named" object.  The most appropriate would be a
named message port.  (Named libraries are another example that is
less applicable to you).  Under 2.0, we have named screens as well.

>============= Ken Jamieson: uunet!tronsbox.xei.com!tron1  ==================

     Peter
--
     Peter Cherna, Software Engineer, Commodore-Amiga, Inc.
     {uunet|rutgers}!cbmvax!peter    peter@cbmvax.cbm.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Very strange... the window is broken on both sides."