%% Regarding Re: FVWM: AutoRaise;
%% Jose M. Pereira <pereira_at_cocaina.inesc.pt> writes:
jmp> That's why I find the "default" 500ms timeout a bit
jmp> tight. 750-1000 is more like it (and more than that is too
jmp> sluggish).
OK, I'll try that.
jmp> Hmm. Yes, that's how it works (should work). I'm sure there is
jmp> a catch mixing deiconify/raise/focus/whatever events, but the
jmp> most common trouble is the timing. Unix/X is not real-time, you
jmp> know... A thorough check of all event timestamps (possible in
jmp> 2.0!) is REALLY complicated.
Ah. I didn't think of that. Well, humph. I wonder if there's a simple
way to absolutely verify that it's a delivery time/order from the server
problem vs. some kind of bug in the FvwmAuto code?
jmp> Welllll... The prototype I have is not a patch, but a *new*
jmp> module, written in Python.
Uh, never mind :)
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
Senior Software Engineer Bay Networks, Inc.
-----------------------------------------------==<
http://www.baynetworks.com/>-
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions--Bay Networks takes no responsibility for them.
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Oct 16 1995 - 14:30:42 BST