On 05-09-2017, at 8:45 PM, John McIntosh johnmci@smalltalkconsulting.com wrote:
BTW also lost over the years was a check for the interrupt keyboard sequence that would fire the interrupt semaphore. That code I think got moved into the image event processing logic. Perhaps not workable if that logic is busy processing bad (or too much) data.
Yeah, I’ve mentioned this a few times too. I still claim the VM needs to handle the lowest level of this since I see too many opportunities for the image being a little distracted by the very problem that you want tointerrupt.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim A computer's attention span is only as long as its extension cord.