ok, where I wrote 'at' before I really meant 'interval'. the 'at' attribute works really fine.
the 'interval' attribute accepts the new value but uses the old one. here is a quick example to what I meant: 1 - Create a timer watcher with a high period (e.g. 60) 2 - Create it parked, so it won't run 3 - the $watcher->interval; reports 60. 4 - set it to lower value (e.g. 1) $watcher->interval(1); 5 - the $watcher->interval; reports 1 (as expected) 6 - start the watcher $watcher->start; 7 - the even will occurr just 60s later and not 1s. This does not happens when 'at' is used. So, I think I might have hit a bug. Regards, Raul Dias >Hi, > >I noted that the 'at' attribute in a timer watcher is >read-only. > >This makes hard to reuse the same watcher several times >with diferent values for it. > >Does it "have" to be read-only? > >How much does it cost for an application to destroy/cancel >a timer watcher and create a new one a few times per second >instead of reusing a pre-existent one? > >I am using timer watchers to delay proccess. >There might be 2 to 60 concurrent timerwatchers >and they may delay from tenths of miliseconds to a few seconds. > > >Regards, > >Raul Dias >
