On Mon, Sep 16, 2002 at 04:58:19PM +0000, Mikhael Goikhman wrote:
> On 16 Sep 2002 18:10:24 +0200, Dominik Vogt wrote:
> > 
> > On Mon, Sep 16, 2002 at 01:57:27PM +0000, Mikhael Goikhman wrote:
> > > In FvwmConsole type 2 Schedule commands, like:
> > > 
> > >   Schedule 20000 5001 Beep
> > >   Schedule   100 5002 Iconify
> > > 
> > > This is currently effectivelly equivalent to:
> > > 
> > >   Schedule   100 5002 Iconify
> > >   Schedule   100 5001 Beep
> > 
> > Fixed.
> 
> It is better now. But I don't know whether timing is fixed. Do the
> following: open xdaliclock and FvwmConsole. Type the first command and
> repeat it in 5 seconds.
> 
>   Schedule 10000 Beep
> 
> Immediatelly after the first and the second command move the mouse to
> another window. You may get different results. Sometimes it's ok. But the
> chance is you hear the first Beep much earlier than in 10 seconds.
> Sometimes I don't hear the second Beep (they probably unite to one).

That's why the man page reads "The command is executed after
*about* delay_ms milliseconds".  For performance reasons, the X
server time is not queried each time a command is scheduled.
Therefore, a command may be executed *much* earlier than the
delay specified if no event came in from the X server for a while.
I had to add this performance hack because it was really easy to
slow down fvwm dramatically before.

> > Never heard of a command log.  Is that something new?
> 
> --enable-command-log was added in 2.3.32.
> 
> I think I prefer the format "%c: %s" to your "type %d, cmd '%s'", because
> the second does not make the log more readable/parsable, just increases
> it. The latters may be 'E', 'M' (module), 'L' (menuloop), 'P', 'S'.

No problem:

 - = No context
 E = Event
 M = Module
 m = menu
 P = paging
 S = Sceduler

Bye

Dominik ^_^  ^_^

 --
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to