On Wed, Jul 05, 2006 at 01:22:40PM -0400, Dan Espen wrote: > "Viktor Griph" <[EMAIL PROTECTED]> writes: > > On Wed, 5 Jul 2006, Scott Smedley wrote: > > > > > Hi Dominik, > > > > > >> Can you have multiple peridic commands or just one? > > > > > > Multiple. > > > > > >> I suggest to replace the command "Periodic" with some option to the > > >> Schedu > > le > > >> command > > > > > > The current specification for Schedule is: > > > > > > Schedule delay_ms [command_id] command > > > > > > So, would something like the following do? > > > > > > Schedule delay_ms [command_id] ["Periodic"] command > > > > > > Perhaps someone has a better suggestion? > > > > > > > I think the above is good. The only problem with it is that if someone has > > a function named Periodic and use to execute that with Schedulte the above > > will break that config. One way to avoid that, and also give room for more > > possible options to Schedule in the future, is to put options before the > > delay. That way any string before the delay number could be read as an > > option. So
> > Schedule [Periodic] delay_ms [command_id] command > > > > would be a possible easier to parse syntax. Yes, I'd prefer "Periodic" as the first parameter (it's easier to parse, and easier to understand). > Schedule delay_ms x repeat_ms [command_id] command > > Ie: > > Schedule 1000 x 2000 .... > Schedule x 5000 .... Hm, do we really need this? I know that my fvwm_periodic function has a repeat interval off 15s and an initial delay of 3s, but that could as well be written as Schedule 3000 function fvwm_periodic Schedule periodic 15000 function fvwm_periodic (well in that case the first delay is 3s, the second 12s and after that it's 15s, but that's fine in that case). In any case, in my script the initial delay is there to give FvwmButtons time to come up, but it's not a safe way to do it. Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED]
signature.asc
Description: Digital signature
