SEND IN TIMe

[Björnke von Gierke]

a send in time message will be postponed if there's too much going on,  
or if an endless loop is running (and thus blocking rev). but after  
things have calmed down, it should fire. so you can't trust that send  
in time is running precisely at the given interval, but you should be  
able to depend on it firing _somewhen_, and not get lost. So if you  
expect the time to be divisible trough 7 minutes (or any other time  
interval), then your handler will not run correctly.

make sure that your handler notifies you, make it beep three time if  
necessarily. I often think my code is not executed because of a bug,  
only to find out that i have added overzealous error checking, which  
makes the handler not give me notice because the property "error  
checking" is not true (for example). because i added a check that  
never could be true, it would not update a status field or run any of  
my dozens of beeps, answer dialogs or "put into msg", which i had  
added over the evening. took me hours to find out that problem, and  
the code i actually wanted to test worked fine the first time! :(

did you check if rev is running an endless handler, a blocking loop or  
a similar task (for example "wait" can block the whole of rev, if used  
wrongly).

do you use cancel? if yes, try to comment out the cancel code, maybe  
you are cancelling the wrong message?

what do the pendingmessages say in your case, is the message really  
gone into the void, or maybe it's set to something strange?

it also might be a platform specific thing. what os, and what rev  
version is this, is it a standalone, or in the ide? for example, i had  
something similar with sockets on linux but on mac os x, any such  
problem never happened to me.

some random thoughts that i'd want to be checked, before i could  
actually make a guess if it could be a bug or not.

bjoernke

On 21 Oct 2009, at 01:33, Terry Dennis wrote:

> OK, I've finally had my fill of this glitch.  I haven't been able to  
> figure out what causes it, so I will describe the process here and  
> see if anybody else can figure out a work-around, or agrees that  
> it's a bug.
>
> "SEND message TO ME IN nnn SECONDS" works fine as long as there is  
> nothing else happening in my PC at the time.  I've had it run for  
> entire weekends with no problems.  The interval is set to 7 Minutes.
>
> However, during weekdays when I am doing some other activity, it  
> occasionally hiccups.  It happens several  times during the day --  
> where "several" can be as many as a dozen, depending on how busy I  
> am.  I frequently have multiple non-Rev windows open performing  
> several different tasks, some of which are CPU intensive.  That's  
> when my Rev application doesn't re-trigger itself.  At least it  
> doesn't appear to.
>
> It appears that the message is not sent -- or not received?  Maybe  
> the message is triggered only if Rev gets control during the EXACT  
> second (tick?) that it's supposed to be sent, and Rev doesn't get  
> control until AFTER that second?  There is nothing in the message  
> handler that checks for the time it is received.  It just takes the  
> message and does its thing.
>
> Any thoughts?
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution



-- 

official ChatRev page:
http://bjoernke.com?target=chatrev

Chat with other RunRev developers:
go stack URL "http://bjoernke.com/chatrev/chatrev1.3b3.rev"