From Gary Colville · 1996-04-09 03:09 · #69575 in GRAND_PRIX
Oh no! On 05 Apr 96 that loony Gordon McVey wrote to Gary Colville : GM> Read the HTML docs you get with Aweb. I have. I get the impression that the guy who wrote them knows very little about MUI. One thing I'd like to know, Gordon - How deep is your knowledge of MUI? How much code have you written that uses MUI? GM> MUI's internal models are for co-operative multitasking. Rubbish. As I said before, MUI has nothing to do with multitasking. I suggest you try writing code under MUI before you start spouting tosh like this. GM> This means that, if a MUI app is not ready to handle an input event, GM> the GUI will not respond no matter how much you click/use hotkey/swear GM> at it. Under Intuition, the GUI is handled by a seperate task which The user should *never* be in a position to click on gadgets while the application isn't able to process the event. The gadgets should be disabled or the app should put up a busy pointer. GM> queues up input events. If you click an Intuition gadget, it will GM> respond immideately, no matter what. If the task the input was ment GM> for is not ready to recieve it, it gets queued, so the task can GM> process it as soon as it's ready So the user clicks on several gadgets to try and get a response, then when the app wakes up it tries to process all those clicks. At best this will result in confusion as the app goes nuts, at worst the user may loose data. IMHO it's better to ignore any input while the app is busy, as MUI does. Of course, it's better never to let the user get into this situation. +------------------+----------------------+-------------+ | Gary Colville | A1200/030 10Mb 36MHz | Member: | | Fido 2:259/68.19 | 1270Mb IDE 4xCD-ROM | Team AMIGA | +------------------+----------------------+-------------+ ... Sex is better than logic. You can't prove it, but it is. --- Cyclone FTN 0.75a * Origin: The Old Bugs Home (2:259/68.19)