by Tdarcos » Sun Jun 10, 2012 7:49 pm
Roody_Yogurt wrote:It is possible to do in z-code, as it was done in Infocom's Border Zone, but I'm not sure how much there support there is for that on the library-side of things, though. Nikos' TADS example is probably the best example you're going to find.
You once posted about this before, pinback, and that got me thinking about how one would do it in Hugo. Well, the main thing is, it's totally not possible, as Hugo really can't do anything while it's waiting for input.
Well, technically true if you don't allow a different set of responding events after the input depending on how long the user waited after replying. You could get near-real time given a readable clock.
I can't remember if Hugo has an accessible timer; if it doesn't, then you're right, there would not be any way to do this in Hugo.
Now, I think someone got a simulated input or something via a Tetris-like game or something.
The big problem, that most people don't realize, is that Microsoft Windows is actually a "transaction monitor system" in which an application runs until it needs input or some response, at which point it effectively "quits" and hands control back to the system. The application is dead and is not operating until an event occurs. A mouse move or click, a keystroke, a timer interrupt, all can then restart the application.
When a program goes runaway and you get an hourglass or simply no redraw of the screen, it means it's not responding to events and is failing to quit every so often.
Now, if the Hugo runtime and the language supported Windows-type events then it would be a different thing and you could have it doing things while waiting for input.
[quote="Roody_Yogurt"]It is possible to do in z-code, as it was done in Infocom's Border Zone, but I'm not sure how much there support there is for that on the library-side of things, though. Nikos' TADS example is probably the best example you're going to find.
You once posted about this before, pinback, and that got me thinking about how one would do it in Hugo. Well, the main thing is, it's totally not possible, as Hugo really can't do anything while it's waiting for input.[/quote]
Well, technically true if you don't allow a different set of responding events after the input depending on how long the user waited after replying. You could get near-real time given a readable clock.
I can't remember if Hugo has an accessible timer; if it doesn't, then you're right, there would not be any way to do this in Hugo.
Now, I think someone got a simulated input or something via a Tetris-like game or something.
The big problem, that most people don't realize, is that Microsoft Windows is actually a "transaction monitor system" in which an application runs until it needs input or some response, at which point it effectively "quits" and hands control back to the system. The application is dead and is not operating until an event occurs. A mouse move or click, a keystroke, a timer interrupt, all can then restart the application.
When a program goes runaway and you get an hourglass or simply no redraw of the screen, it means it's not responding to events and is failing to quit every so often.
Now, if the Hugo runtime and the language supported Windows-type events then it would be a different thing and you could have it doing things while waiting for input.