Re: TimeSetEvent


"Gert Baars" <g.baars13@xxxxxxxxx> wrote in message
news:9df32$45673ed1$3ec23508$15477@xxxxxxxxxxxxxxxxx
With TimeSetEvent a Callback function is assigned
to execute at an interval.
In the callback a COM-port is polled and data is
processed. A certain loop within the callback
sometimes hangs (or is not exectuted) while
another runs normally. All processing is done within
the intervaltime (20mS). Should certain global
variables be protected to avoid this?

The timer callback executes in its own thread.

some vcl elements are not threadsafe, form var states
may not be as expected, some vcl calls might not execute.


.

Relevant Pages

  • Re: [patch 1/7] Immediate Values - Architecture Independent Code
    ... static unsigned int stopmachine_num_threads; ... * help our sisters onto their CPUs. ... all the other CPUs will execute the callback concurrently. ...
    (Linux-Kernel)
  • Re: Sockets Beginreceive not working correctly.
    ... the beginrecieve is ignored. ... there's no reason to expect your callback method to be ... BeginReceivewould not normally execute the callback in any case. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: How can I tell if my Ribbon is visible?
    ... Depending on the performance cost of executing the callback, you could do this whenever your event gets triggered, but before you execute your parsing. ... The callback will be executed once your tab is brought into the foreground. ... You can do this approach with any of your controls and callbacks, there is no need to create a special one for it. ...
    (microsoft.public.office.developer.com.add_ins)
  • Re: Sockets Beginreceive not working correctly.
    ... -- By the time you get to stepping through the code, the second part of your data hasn't yet been sent. ... there's no reason to expect your callback method to be executed. ... BeginReceivewould not normally execute the callback in any case. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: In asynchronous model, IAsyncResult.AsyncWaitHandle signaled first, or AsyncCallback invoked fir
    ... The correct sequence should be ... because the callback function might wait on the ... Just because the WaitHandle gets set, that doesn't mean that the thread waiting on it will run immediately. ... Until that thread exhausts its quantum or hits some sort of wait state itself, the thread waiting on the WaitHandle still isn't going to execute. ...
    (microsoft.public.dotnet.languages.csharp)