Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) Newsgroups: comp.lang.forth Subject: MS Windows 3.0 Message-ID: <2683.UUL1.3#5129@willett.pgh.pa.us> Date: 28 Apr 91 03:32:28 GMT Organization: (n.) to be organized. But that's not important right now. Lines: 40 Date: 04-24-91 (08:27) Number: 1989 of 1989 (Echo) To: DENNIS RUFFER Refer#: 1973 From: JACK WOEHR Read: NO Subj: MS WINDOWS 3.0 Status: PUBLIC MESSAGE Conf: FORTH (58) Read Type: GENERAL (+) -> Can anyone out there share their experiences in working with this -> "mind switch"? I'm not sure about Unix, but the Mac does work under -> this Message Processing architecture. How does this work with -> Forth's KEY and EXPECT? The Amiga, a fully-multitasking operating system, has a message- based architecture. Like many multitasking systems, an Amiga application should Wait(messages_mask) in between activities. The trick is that in a GUI you have to set the bits for several different types of messages and be ready to handle them when they come in. So even simple words like KEY before they call Wait() have to set several different bits (keystroke, mouse select, close button, etc) that indicate what kind of messages they are willing to accept. Then when a message *does* come, they have to process whatever message it might be within the range of messages they were willing to accept. If you get too frazzled, Dennis, you oughta look at contracting this out :-) =jax= NET/Mail : RCFB Golden, CO (303) 278-0364 VESTA & Denver FIG for Forth! <<<>>> ----- This message came from GEnie via willett. You *cannot* reply to the author using e-mail. Please post a follow-up article, or use any instructions the author may have included (USMail addresses, telephone #, etc.). Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp