World: r3wp

hmm, but this stil doesn't address my question no?

It says the resolution is one milisecond which is cool. So why wait 
10ms doesn't let  CPU idle enough so it is not at 100% of usage?

I'm with Richard on this.

I seem to recall that .002 was a lower limit that could cause issues 
in R2 if you went below that.

Yes, I'm not talking about precisison..this is not important in the 
tests above. The problem is why empty loop with enough IDLE time 
for CPU is making it at 100%

probably only Carl can answer this ...

Cyphre, I'm not sure if this is relevant, but timers under OSX are 
currently broken, so wait will eat CPU no matter what the wait period 
is. Maybe something broke in the last few versions?

I don't know about OSX, sorry. I refer to Win versions just to be 
clear.

Also I just tried to test under some prehistoric alpha prototype 
R3 versions and the 100% usage is there so I wonder noone noticed 
that so far :)

Right. It seems that it's overhead in WAIT.

Gregg, yes in R2 it looks the resolution that can be measured under 
Windows is ~10ms and you start to burn your CPU at 100% when you 
WAIT 0.0001 which means in R2 the same as WAIT 0.

Right. I thought maybe R3 had an artifact of that, but it doesn't 
seem so. CPU use goes up as you decrease the wait time, there doesn't 
seem to be a magic threshold.

Gregg, yes it looks like that...either there is some bug in WAIT 
or WAIT is not letting CPU to get IDLE state anymore from some reason.

Agreed.

The only possibly related thing I can find is http://curecode.org/rebol3/ticket.rsp?id=379&cursor=30

I think the OS_Wait() function in Host kit could give us some answer. 
I'll try to recompile with some debug info....

Is a simple LOOP with a WAIT in it enough for the bug report?

Ah, OK. That sounds good.

Are you Guys using wait , instead of time events in your GUI ?

yes,  the above discussion is wait command inside loop.
BTW what time events you mean?

like in R2 the time events generated by the rate propertie

AFAIK there is no RATE in R3. Or am I missing something?

there's no rate but you can generate time events aswell

not documented though

you mean like make event! [] right?

yep

but constructing an event is not enough, you have to know where to 
push it :)

ok, but even if you generate own events you need to WAIT at some 
point so the CPU is not at 100% no?

no, it depends of the duration of the process triggered by your events, 
if it takes too much time, it will froze the CPU obviously.

i have not made tests so far actually

just guessing

can you post any example if it is not too big?

i could, perhaps tomorrow, i have not the source at my home.

The principle is simple.

At startup, I build an event time!, the I push it in the block located 
at system/view/event-port/state.

And In my global event handler, each time I receive this event, I 
repush it immedialtly in the queue.

I receive 1000 time! events per seconds in My tests, but it mights 
depend of the speed of your UC

ok, no hurry...I'll also try to play with it later.

hmm, I pushed event into the event-port/state but nothing happened 
here. the event is still there and was not send to my global handler.

did you do a do-events ?

yes, tried both do-events or just calling VIEW

i will post it tomorow, it tried only on XP

is that some new feature? I'm using 2.100.97.3.1 release under Win 
XP

i don't think so, actually it's a trick i discovered accidentaly. 
I don't thing Carl thought about it

i used 97 too

do I need to set the event properties in some specific way?

i just made
make event! [type: 'time port: port-event]
(yes you need to add the port-event, if not it doen't work)

doesn't work here even if I put the reference to event port inside 
the event

Hmm... i will post my complete test then.

How did you created the port-event ?

I just put there reference to system/view/event-port

event-port: system/view/event-port: open event:// 
And then you added you handler at  port-event/awake
right  ?

I'm using the official init-view-system so the sequence looks like:
init-view-system
p: system/view/event-port

insert system/view/event-port/state ev: make event! [type: 'time 
port: p]
...