acm131@eric.ccs.northeastern.edu (Craig Scott Lennox) (11/30/89)
What is the way, under AmigaDOS, to put up a dialogue box which prompts the
user for information, and disallows context switches, opening new windows,
pulling down other screens, etc. Will doing a forbid() be good enough, or
is there more to it? Basically, I want Amy to STOP EVERYTHING until I get
the information. (or the user cancels out of the dialogue box) Yes, I
realise it's a pain, but I want to eliminate unpredictable states. It
seems to me there mucst be a way, because I see other software doing it.
Using Lattice C, if possible.
Thanks,
Craig.
///
/// acm131@eric.ccs.northeastern.edu
\\\///
\XX/ "Hey OS/2, wanna race??"new@udel.edu (Darren New) (11/30/89)
In article <4995@nigel.udel.EDU> Craig Scott Lennox <acm131@eric.ccs.northeastern.edu> writes: >What is the way, under AmigaDOS, to put up a dialogue box which prompts the >user for information, and disallows context switches, opening new windows, >pulling down other screens, etc. Well, DisplayAlert() is pretty evil. However, it only gives you a boolean choice. I'm not exactly sure what it disables. Exactly what "states" are you trying to avoid? There is almost certainly a better way (like locking intuition, coding in semaphores, ...). -- Darren
acm131%eric.ccs.northeastern.edu@cunyvm.cuny.edu (12/06/89)
What is the way, under AmigaDOS, to put up a dialogue box which prompts the
user for information, and disallows context switches, opening new windows,
pulling down other screens, etc. Will doing a forbid() be good enough, or
is there more to it? Basically, I want Amy to STOP EVERYTHING until I get
the information. (or the user cancels out of the dialogue box) Yes, I
realise it's a pain, but I want to eliminate unpredictable states. It
seems to me there mucst be a way, because I see other software doing it.
Using Lattice C, if possible.
Thanks,
Craig.
///
/// acm131@eric.ccs.northeastern.edu
\\\///
\XX/ "Hey OS/2, wanna race??"new%udel.edu@cunyvm.cuny.edu (12/06/89)
In article <4995@nigel.udel.EDU> Craig Scott Lennox <acm131@eric.ccs.northeastern.edu> writes: >What is the way, under AmigaDOS, to put up a dialogue box which prompts the >user for information, and disallows context switches, opening new windows, >pulling down other screens, etc. Well, DisplayAlert() is pretty evil. However, it only gives you a boolean choice. I'm not exactly sure what it disables. Exactly what "states" are you trying to avoid? There is almost certainly a better way (like locking intuition, coding in semaphores, ...). -- Darren
33014-18@sjsumcs.sjsu.edu (Eduardo Horvath) (12/08/89)
In article <5389@nigel.udel.EDU> acm131%eric.ccs.northeastern.edu@cunyvm.cuny.edu writes: > >What is the way, under AmigaDOS, to put up a dialogue box which prompts the >user for information, and disallows context switches, opening new windows, >pulling down other screens, etc. Will doing a forbid() be good enough, or >is there more to it? Basically, I want Amy to STOP EVERYTHING until I get >the information. (or the user cancels out of the dialogue box) Yes, I >realise it's a pain, but I want to eliminate unpredictable states. It >seems to me there mucst be a way, because I see other software doing it. > One possibility is to set the WINDOW_DEACTIVATE (or the eqivalent, no RKMs handy) in your window, and whenever the user selects something else, do an ActivateWindow() and a WindowToFront() and a ScreenToFront(). That ought to get his attention. >Using Lattice C, if possible. > Craig. > /// acm131@eric.ccs.northeastern.edu Disclaimer: No, I didn't try it, don't blame me for any fireworks. ---- Eduardo Horvath | Director, Campaign to Free Doctor Science Send your contributions to: 33014-18@sjsumcs.SJSU.EDU "Why don't you stop your whining, and get back to work!" - Doctor Science
33014-18%sjsumcs.sjsu.edu@cunyvm.cuny.edu (12/15/89)
In article <5389@nigel.udel.EDU> acm131%eric.ccs.northeastern.edu@cunyvm.cuny.edu writes: > >What is the way, under AmigaDOS, to put up a dialogue box which prompts the >user for information, and disallows context switches, opening new windows, >pulling down other screens, etc. Will doing a forbid() be good enough, or >is there more to it? Basically, I want Amy to STOP EVERYTHING until I get >the information. (or the user cancels out of the dialogue box) Yes, I >realise it's a pain, but I want to eliminate unpredictable states. It >seems to me there mucst be a way, because I see other software doing it. > One possibility is to set the WINDOW_DEACTIVATE (or the eqivalent, no RKMs handy) in your window, and whenever the user selects something else, do an ActivateWindow() and a WindowToFront() and a ScreenToFront(). That ought to get his attention. >Using Lattice C, if possible. > Craig. > /// acm131@eric.ccs.northeastern.edu Disclaimer: No, I didn't try it, don't blame me for any fireworks. ---- Eduardo Horvath | Director, Campaign to Free Doctor Science Send your contributions to: 33014-18@sjsumcs.SJSU.EDU "Why don't you stop your whining, and get back to work!" - Doctor Science