using an async timer is a good solution to check for events,
especially if there is no regular loop in your program.
Maybe you want to Reset the timer also when no events have
been processed?
Bool_t MyTimer::Notify() {
gClient->HandleInput();
Reset();
return kFALSE;
}
Notice that gClient->HandleInput() only processes GUI events.
TSystem::InnerLoop() will process all events (sockets, sync timers).
If you only expect GUI events the above is fine.
Cheers, Fons.
PS: "delete mytimer" will also call gSystem->RemoveTimer()
Andrej Filipcic wrote:
>
> On Fri, 27 Mar 1998, Fons Rademakers wrote:
>
> Dear Fons,
>
> actually I found another way to do that. If there is no input, a call to
> gSystem->InnerLoop();
> would wait for an input. Is this correct?
> So, I created async MyTimer from TTimer and implemented
>
> Bool_t MyTimer::Notify() {
> if(gClient->HandleInput()) Reset(); // Should I use gClient->Notify()?
> return kFALSE;
> }
>
> Then, I do
>
> MyTimer* mytimer = new MyTimer(100);
> gSystem->AddTimer(mytimer);
> // Loop
> gSystem->RemoveTimer(mytimer);
> delete mytimer;
>
> This handles Gui events correctly.
>
> Andrej
> >
> > you should call once in while in your DAQ loop the function:
> >
> > gSystem->InnerLoop();
> >
> > this will flush pending graphics, socket and synchronous timer
> > events. When pending events have been processed it will return, when
> > no events are pending it will wait for an event to happen. To
> > prevent this from blocking your app use a timeouttimer like is done
> > in the TMonitor class (http://root.cern.ch/root/html/src/TMonitor.cxx.html).
> > See TMonitor::Select(Long_t timeout). I might provide a
> > TSystem::InnerLoop(Long_t timeout), but for the time being add the time-out
> > like in the Select method.
> >
> > Cheers, Fons.
-- Org: CERN, European Laboratory for Particle Physics. Mail: 1211 Geneve 23, Switzerland Phone: +41 22 7679248 E-Mail: Fons.Rademakers@cern.ch Fax: +41 22 7677910