On 23 Jun, Mark Anderson wrote:
>> > This is because you would be better off using
>> >
>> > AddToFunc Circ "I" Focus
>> > + "I" Raise
>> >
>> > or if you are fussy about style (like I am)
>> >
>> > AddToFunc \
>> > "I" Focus
>> > + "I" Raise
>> >
>> > Either of these should fix your problem.
>>
>> Why?
>>
>> Dominik
>>
> Does anyone know the answer to this question?
> Why does an empty line on the AddToFunc line cause a large delay?
> If I had a preprocessor creating these files, and selecting from a
> predefined set of commands to put in the function, I find it simpler,
> and IMHO elegant to define the function that will be modified without
> tacking the definition onto the same line.
>
> For menus at least a title definition makes sense on the first line.
This is an artifact from the original "intention" of functions, which
was to provide a set of functions that could be performed when a
titlebar button is pressed.
What happens if there isn't an "immediate" "I" after the AddToFunc Circ
is that fvwm2 pauses for a certain amount of time in order to detect if
a "double click" happened. Now, since functions are no longer only
spawned by title bar buttons, this pause isn't needed. I think the
weird syntax was to tell fvwm2 NOT to ever delay for a double click.
--
Larry Gensch larry.gensch_at_digital.com
"Realize you should why a Jedi his lightsaber as a toothpick should not use!"
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Jun 23 1999 - 12:28:16 BST