OpenEuphoria

Re: Thanks

• Posted by jbrown105 at speedymail.org Jun 17, 2003
• 616 views

On Tue, Jun 17, 2003 at 11:21:19PM +0100, Pete Lomax wrote:
> 
> 
> On Tue, 17 Jun 2003 17:46:35 +0000, Jonas  Temple <jtemple at yhti.net>
> wrote:
> 
> >that the mouse pointer doesn't get updated unless you stick a few 
> >doEvents() in the code 
> 
> Well, obviously, if you are running any kind of code beyond just
> instant reaction to gui events, you really really MUST litter it with
> doEvents() calls.
> 
> If you, or anyone else, does not understand this, you do need to spend
> some time thinking about it, otherwise you will never EVER understand
> event-driven code. My apologies for being blunt.
> 
> Pete
> 

That makes sense with cooperative multitasking. Preemptive multitasking
doesn't really need this however.

Also the need to release the cpu is present in all OSes which allow
multitaskingm
not just event driven programs.

I write this because I don't understand why one must litter the code with
doEvent() calls. I've never had to do this with GUI programming in Linux.
(In fact, aside from sleep(), Linux seems to not even HAVE a doEvents()
equivelent,
tho I haven't looked very hard for one.)

I know that doEvents() comes from Win 3.1, which was a cooperative OS, but
why do more modern Windoze OSes need it?

Very curious,
jbrown

> 
> 
> TOPICA - Start your own email discussion group. FREE!
> 
> 

-- 
 /"\  ASCII ribbon              | http://www.geocities.com/jbrown1050/
 \ /  campain against           | Linux User:190064
  X   HTML in e-mail and        | Linux Machine:84163
 /*\  news, and unneeded MIME   | http://verify.stanford.edu/evote.html