Delayed uiEventFor: aWindow ...

> -----Original Message-----
> From: Dennis Smith [mailto:[hidden email]]
> Sent: Wednesday, July 18, 2007 11:55 AM
> To: VWNC,
> Subject: Delayed uiEventFor: aWindow ...
>
> (VW 7.4.1, WinXP SP2).
>
> I sometimes find that an event queued for a window using "uiEventFor: "
> does not occur for a while -- maybe 10 or 15 seconds.
>
> Everything is quiet, the window will respond if I click in it (its the
> current window),
> but the queued event just does not occur for a while.
>
> This occurs in a number of instances, but one of them is my cursor
> handling
> where I turn the cursor to a wait and queue an event for the window to
> make it
> back to normal -- and the wait cursor will just sit there.
>
> It occurs in other instances too.
>
> Anyone seen this kind of thing??
>
> --
> Dennis Smith                         +1 416.798.7948
> Cherniak Software Development Corporation   Fax: +1 416.798.0948
> 509-2001 Sheppard Avenue East        [hidden email]
> Toronto, ON M2J 4Z8              sip:[hidden email]
> Canada         http://www.CherniakSoftware.com
> Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP

> (VW 7.4.1, WinXP SP2).
>
> I sometimes find that an event queued for a window using "uiEventFor: "
> does not occur for a while -- maybe 10 or 15 seconds.
>
> Everything is quiet, the window will respond if I click in it (its the
> current window),
> but the queued event just does not occur for a while.
>
> This occurs in a number of instances, but one of them is my cursor
> handling
> where I turn the cursor to a wait and queue an event for the window to
> make it
> back to normal -- and the wait cursor will just sit there.
>
> It occurs in other instances too.
>
> Anyone seen this kind of thing??
>

>
> Victor
>
> ===================================================
>
> Dennis Smith wrote:
>> OK --- thought people might be interested in what this was ...
>>
>> Seems that my clock on my PC was a bit nuts.  It was losing time
>> on the order of 1 second every 20 or 30 seconds -- most of the time,
>> then it might mess up 20 seconds or the largest I saw was 49 seconds
>> in a period of 2 minutes -- in desperation I had set my time-sync's
>> on the PC
>> to be every 2 minutes.
>>
>> Just to be sure it was not my imagination, I created a 50ms (approx)
>> busy-loop in VW
>> and computed 2000  "Time millisecondClockValue" values, and then
>> computed the
>> duration between each.
>>
>> Most were between 40 and 60ms -- but 4 on average were -1300 or so ms
>> difference.
>> This kind of thing can play havock with "Delay" or with
>> "millisecondsToRun: ..." both of
>> which were causing me problems.
>>
>> Specifically, in my cursor problem below, the code that reset the
>> cursor did
>>    (Delay forMilliseconds: 1) wait
>> and this would wait randomly and sometimes up to 20 seconds or more.
>>
>> I should have noticed that I never had the problems on my home PC,
>> only at the office,
>> but I failed to note that.
>>
>>
>>
>>
>> Dennis Smith wrote:
>>> (VW 7.4.1, WinXP SP2).
>>>
>>> I sometimes find that an event queued for a window using "uiEventFor: "
>>> does not occur for a while -- maybe 10 or 15 seconds.
>>>
>>> Everything is quiet, the window will respond if I click in it (its
>>> the current window),
>>> but the queued event just does not occur for a while.
>>>
>>> This occurs in a number of instances, but one of them is my cursor
>>> handling
>>> where I turn the cursor to a wait and queue an event for the window
>>> to make it
>>> back to normal -- and the wait cursor will just sit there.
>>>
>>> It occurs in other instances too.
>>>
>>> Anyone seen this kind of thing??
>>>
>>