[futurebasic] Re: [FB] HANDLEEVENTS on web site

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : September 2000 : Group Archive : Group : All Groups

From: Chris Stasny <staz@...>
Date: Fri, 29 Sep 2000 08:44:04 -0500
I put it on the web site.

>Dear Chris,
>
>Now I understand the history of Mac
>
>I think it is a good idea to put your explanation in the appendix or section
>of HANDLEEVENTS of Reference manual.
>
>--
>Masa
>masa.nakao@...
>
>
>on 00.9.25 11:41 PM, Chris Stasny at staz@... wrote:
>
>  >>
>  >>> Thank you for your comment about HANDLEEVENTS.
>  >>>
>  >>> FB2's HANDLEEVENTS is potentially harmful???
>  >
>  >
>  > I think we are all missing the point here.
>  >
>  > In 1984, Macs could only handle one application at a time. Therefore,
>  > there was a constant, non-stop checking for events.  This was done
>  > thru a toolbox named GETNEXTEVENT. It was fast, but it also preempted
>  > everything else on the computer. In other words, you could not
>  > download a file while you worked in a word processor.
>  >
>  > Later, a group of independent programmers developed the MultiFinder
>  > which allowed two or more apps to run at the same time. Now it became
>  > necessary for applications to get along and quit hogging the
>  > microprocessor, so apple created WAITNEXTEVENT.
>  >
>  > WAITNEXTEVENT is almost identical to GETNEXTEVENT, except that it
>  > does not return a constant stream of null events. With WAITNEXTEVENT,
>  > you establish a time frame (usually 1-3 ticks) and the toolbox will
>  > allow background apps to process there stuff instead of sending
>  > useless null events to your application.
>  >
>  > This delay does not affect the operation of your application. Regular
>  > events come thru just as fast as the machine allows. Window updates,
>  > mouse clicks, etc are instantly processed. But if there is absolutely
>  > nothing going on in your application, a few microseconds are devoted
>  > to seeing if some other app has to process an event.
>  >
>  > FB's HANDLEEVENTS statement will allow you to use either. If you set
>  > gFBEvtWneTicks to zero, then it will operate in the rude manner used
>  > by the original Mac systems and will prevent other applications from
>  > operating correctly in the background. If you set gFBEvtWneTicks to a
>  > value of 1 or higher (3 is usually recommended) then the app behaves
>  > in the correct manner. It still gets every event instantly as it
>  > becomes available, but when no events are pending, it will allow
>  > other apps a tick or two do to their work.
>  >
>  >
>  >
>  > Best,
>  >
>  > -STAZ  ~)~
>  >
>  > 800.348.2623 Orders  http://www.stazsoftware.com
>  > 228.255.7086 FAX     mailto:staz@...
>  >
>  > --
>  > To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>
>  >
>
>
>
>--
>To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>



Best,

-STAZ  ~)~

800.348.2623 Orders  http://www.stazsoftware.com
228.255.7086 FAX     mailto:staz@...