bin@primate.wisc.edu (Brain in Neutral) (01/11/91)
Programmer's Guide to MultiFinder p 2-11 says: "The less your application access low memory, the better. Writing to low memory, however, is much more objectionable than reading, and should be avoided. In the long run, low memory will disappear, so try not to depend on it." I take this to mean that if you read or write low memory globals, your application *will* break at some point in the future. On the other hand TN 202 discusses what applications that modify the system event mask should do, e.g., if they need to receive key up events. Part of the technique given is to read the low memory global SysEvtMask and then restore it (i.e., write it) later. The write can be avoided simply by calling SetEventMask() instead, but what does one do to get the system event mask *without* reading the global? Or, does one simply assume that the event mask should be set back to everyEvent - keyUpMask and forget about reading it at the beginning of the application? -- Paul DuBois dubois@primate.wisc.edu