🚀 go-pugleaf

tron1@tronsbox.xei.com (HIM) writes:

>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 ????

Why don't you have the screen memory as part of the message port
structure? 

I am not absolutely positive this would work, but I would imagine that
you could allocate the screen via OpenScreen( &NewScreen ), and copy
the resulting Screen structure into you Message Port Structure.
Your pointers to all the relevent data would be there, which might cause
a problem if you get into an MMU equipped amiga (whose OS knows about it).

Well, perhaps not, but I would not walk through the list.  I would make
the screen info part of the message port, either via pointer in the 
message port, or have the screen as part of the message port.  I am not
sure which is more "proper" as far as kindness to the OS is concerned.
(ie more portable)

brian moffet