LANGREITER.COM plain, simple | |||||||
START INDEX | |||||||
The event! datatype is for GUI (input) events only, not for other types of system events. The universal i/o and signalling mechanism in REBOL consists of ports and 'wait. Timers would be implemented using ports as well. An "event" in its abstract notion is simply "something that happens asynchronously". In REBOL this concept is captured by data arriving at a port and that port signalling the arrival to a pending 'wait call. "Event-driven programming" has nothing to do with the event! datatype. It simply describes a style in which the program waits in a single, central place most of the time, and the program flow is driven by external influences. In REBOL you do this by using ports and 'wait. If you want to handle GUI events as well then ONE of the ports you wait for is the global event-port, but other than that there is no impact on your event loop, and it is certainly not necessary to use the event-port to write event-driven programs. Holger Kruse on REBOL-L, 2002-01-30. |
SEARCH
GET YOUR MOVE ON ALMOST ALL ABOUT YOU So log in, fella — or finally get your langreiter.com account. You always wanted one. Nearby in the temporal dimension: Nobody. ... and 42 of the anonymous kind. Click on for a moderate dose of lcom-talk. This will probably not work in Lynx and other browser exotica. BACKLINKS rebol-notes RECENT EDITS (MORE) films-seen Blood Stone y!kes wet towel B Studio Pilcrow News Nastassja Kinski 2011-10-06-steve 2011-10-06 comment-2011-08-04-1 POWERED BY &c. GeoURL RSS 0.92 FRIENDLY SHOPS Uncut Games bei Gameware OFFEN! Offenlegung gem. §25 MedienG: Christian Langreiter, Langkampfen See also: Privacy policy. |