🚀 go-pugleaf

I am trying to convert an application I have written with MWC 2.0 into a
GEM desk accessory.  I have cut the program down so that it is very simple,
but when it is installed it causes some GEM applications to go bonkers.
Even the GEM desktop bombs at times.  The program doesn't use the 
VDI, and only uses a few AES calls.

I realize that desk accessories should not use malloc(), stdio, or try
to install a menu bar, and they must be careful with use of 
rsrc_load() (my desk accessory doesn't use rsrc_load).  Of course, desk
accessories must follow the usual protocols for window management.

Are there other rules that a desk accessory should follow?  Should 
a desk accessory keep virtual workstation and windows handles after it
has received an AC_CLOSE message?

Is the format of resource files documented anywhere?  No, I don't want
to buy the developers kit.



Karl Rowley
rowley@orville.nas.nasa.gov