%% larry.gensch_at_digital.com writes:
lg> This is an artifact from the original "intention" of functions,
lg> which was to provide a set of functions that could be performed
lg> when a titlebar button is pressed.
lg> What happens if there isn't an "immediate" "I" after the AddToFunc
lg> Circ is that fvwm2 pauses for a certain amount of time in order to
lg> detect if a "double click" happened. Now, since functions are no
lg> longer only spawned by title bar buttons, this pause isn't needed.
lg> I think the weird syntax was to tell fvwm2 NOT to ever delay for a
lg> double click.
Is this really true? I can hardly believe it. I can see
differentiating between, say:
AddToFunc Circ
+ "I" something
vs.
AddToFunc Circ
+ "C" something
where the clicktime is needed if you want to know if you had a
double-click or not (although maybe you really only need to wait if both
a "C" _and_ a "D" are given?)... but differentiating between:
AddToFunc Circ [...anything...]
vs.
AddToFunc Circ
+ [...anything...]
_has_ to be a bug... doesn't it? Isn't this just merely a parsing
issue, and the difference is completely resolved during the fvwm2rc file
parsing at startup?
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
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 - 13:44:10 BST