🚀 go-pugleaf

---

regarding redraw messages: there is a better (i define better as more
general) way of forcing a redraw using the appl_write () function. it
is more tricky but once u master it, it is more like a general interprocess
message passing utility (i.e. send a message to the current appl, or
to and from an accessory). most applications are written with some sort
of evnt_multi () loop that checks for messages, timer events, keyboard
events, and button events. one of the messages which is looked for is
WM_REDRAW.

tim oren's GEM tutorials presented such a "self redraw" code. the code
fragments recently posted are ok to do the actual redraw.

the only trick involved with using the appl_write () code is getting
the correct application id. i was having some problems and found out that
gulam was somehow messing this up. invoked from the desktop, everything
worked fine. most texts on GEM say the appli_init () function returns
an application id (apid). this MAY be the case on PC GEM or with some
compilers on the ST. however, at least with (beloved) alcyon, the AES 
bindings (AESBIND) export a global 16-bit int containing the proper
gl_apid to use. don't use the return value from appl_init (unless your
compiler bindings say it's ok).

main()
{
	extern int	gl_apid;

	appl_init ();

	/* now gl_apid contains the id of THIS application */

}

u can use appl_find () to get the id of any other gem application in memory
(like .acc's).

if youse guys want, i'll post a small example...

-bill

rosenkra@hall.cray.com or rosenkra%boston@hall.cray.com
...!rutgers!umn-sc!hall!rosenkra

(p.s. there was an article back in STart circa 1987 by tom hudson on this
message pipe scheme...)