How do we do that in FB, or is it business as usual with HANDLEEVENTS. How do I set a link in FB. What is the event model that we should be moving toward? >It means that there are additional hooks for preemptive multitasking. >(i.e. you can set a link to automatically call you for a window >update instead of passing thru an event loop.) It does not nullify >HANDLEEVENTS. It does not mean that we can't process preemptive tasks >thru our HANDLEEVENTS key word. > >> >>It looks like HANDLEEVENTS will disappear under OSX. >> >> >> >>How do we deal with this as FB programmers? STAZ Andy anyone? >> > >> > >> >Huh!?! It's not going away. >> >>OK STAZ >> >>What does the following mean then? >> >> >>============================================================ >> >> A P P L E D E V E L O P E R C O N N E C T I O N >> >> N E W S >> >> Issue 224 October 6, 2000 >> >>============================================================ >> Mac OS X Tips & Tricks >> Moving Your Code to Mac OS X: Preemption >> >>The older "polling for events" model imposed by WaitNextEvent is no >>longer necessary under Mac OS X. Carbon and Cocoa applications >>running in Mac OS X can use the new Carbon Event model that will >>allow for more efficient use of processor time. With Carbon Events, >>the event model has changed: instead of your application polling for >>events to discover changing conditions it must respond to, your >>application is called upon as events you wish to respond to arise. >> >>For more information about moving your code to Mac OS X, please see >>http://developer.apple.com/technotes/tn/tn2003.html. >> >>Peter mailto:peter@... >> >> >> >>-- >>To unsubscribe, send ANY message to <futurebasic-unsubscribe@...> > > > >Best, > >-STAZ ~)~ > >800.348.2623 Orders http://www.stazsoftware.com >228.255.7086 FAX mailto:staz@... > >-- >To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>