Multitasking Message Window
4 posts, 4 voices
Andrew Hodgkinson (6)
465 posts
|
This topic has been imported from the old forum. Due to its use of fixed format text, you may need to make your browser view wider in order to see posts with the correct layout. |
Adam (47)
40 posts
|
...e.g. to use in place of *Error This would be particularly useful in !Run files to avoid the need for nasty non-multitasking message windows which bring the whole desktop to a grinding halt in a particularly unhelpful way. Adam P.S. I do actually use a small basic utility to generate such messages in my programs, but an OS solution would be far superior. http://www.snowstone.org.uk/riscos/multierror/ |
Garry (87)
184 posts
|
Adam (47) wrote: > ...e.g. to use in place of *Error > > This would be particularly useful in !Run files to avoid the need for > nasty non-multitasking message windows which bring the whole desktop to > a grinding halt in a particularly unhelpful way. > > Adam To make *all* standard dialogs multi-tasking would be great, obviously apps are made without them in mind, so maybe the WIMP could be convinced to block input into the dialog's owner, but allow it elsewhere? |
James Lampard (51)
120 posts
|
It’s not just about blocking input. The only way the wimp can communicate with the app generating the error is through the returned value of Wimp_ReportError. It won’t be able to call the standard Wimp_Poll routines, so no moving of windows, no redrawing, and definitely no receipt of messages. The best you can probably do is a multitasking error box that turns into a single tasking one, when something happens that the task can’t immediately handle. This could be kinda of implemented by existing apps on an ad-hoc basis, the fact that it hasn’t been indicates that this is difficult and that there will be subtle problems. Still it would be nice if the clock kept running with an error window open. |
