2 ms·
“nothing else happened in the background while you held a menu open“ That was because the OS was hacked (I guess the design looked differently, initially) to r
by Someone 6y ago
“nothing else happened in the background while you held a menu open“
That was because the OS was hacked (I guess the design looked differently, initially) to run on a 8MHz 68000 in 128k of RAM. To make menu opening and closing snappy (necessary because users will open and close menus searching for a menu option), it was implemented by
1. saving the screen bits that would be clobbered drawing the menu.
2. handling menu selection.
3. copying back those bits.
Drawing to the screen could mean writing directly to screen memory, which couldn’t be detected because there was no MMU, but even if it was done using system calls, programs couldn’t be halted when they made such calls. So, step 3 meant changes ‘under’ the opened menu would be lost, so nothing could be allowed to draw to the screen during step 2.
And of course, little of that mattered for the original OS, as it wouldn’t run multiple programs or multiple threads in a program. Step 2 would be the only thing running that was supposed to do screen drawing (with exceptions for drawing the mouse pointer, a feature that just have been fun to implement. Sound and async disk I/O (with its funny software-controlled floppy rotation speed) also would run, but those were limited in what they were supposed to do)
I’m not 100% glad those times are gone. Things were harder to do, but getting anything done felt way more as an accomplishment.