CompuServe Messages

No, for sure I found it. It was the Allocsignal without the FreeSignal in the port clean up. Darwin knows CoComm has enough signal bits running around anyway, I can't afford to go throwing them out the proveribal portal. I figure, one for serial port, one for each console, one for gadget window, one for regular key compare timer, one for general purpose timer, one for review buffer (if it's open), one for auxillary window (file requester, locator, keydefs, palette, sen list, gadget editing window, prefs window) Those don't multitask like the others, so there's only 1 signal used for whichever (if any) of that group is open, but still. <grin>. The compare operation in the function keys was using the timer to limit that amount of time it would wait to see if the text was ever going to come… in my sign in sequence, I use it about 4 times… that's 4 more signal bits! <Gadz!> Pretty soon, you run out of signal bits (frankly, I don't think there are enough available, in general – this is sort of up against the wall now, as far as I'm concerned) and you have the nasty feature. Incidentally, chekc this out: I do the allocsignal, and if it returns (-1) I pop up a requester that says "you don't have a signal bit" and etc. Guess what? According to Tobbes memwatch, low memory gets stepped on right then, no waiting thank you very much. I wonder if the requester (using autorequest here, folks) tries to allocate a signal bit and doesn't check it? Because the trampling occurs before the autorequest window is fully rendered…. makes you wonder if it's the autorequest getting ill, or if AllocSignal goes nutz because it didn't have a signal to give you. Life is so interesting programming this machine. <glazed look>