>>>>> "Mike" == Mike Blatchley <Mike_Blatchley_at_maxtor.com> writes:
>>>>> "Richard" == Richard A Guay <rag_at_asicint.com> writes:
Mike> Chuck,
Mike> Since the early days of fvwm-2, I have seen a problem when using a
Mike> large value for the EdgeResistance timer such as:
....
Mike> However, if a window is being moved or resized when the pointer hits the
Mike> edge, life does not go on _if the pointer is retracted within this time_
Mike> period. Everything is temporarily put on hold for, say, 1second. If it
Mike> enters and exits the pan frame region multiple times before the mouse
Mike> button is released, things can be put on hold for even longer!
....
Mike> I submitted a patch for this a while back, but it seems to have never
Mike> made its way into fvwm. Here's a cleaner patch to fvwm-2.0.43.
Yeah, it must have slipped through the proverbial cracks, as things
often do...
I'll play with it and if things look ok with it, it'll be in 2.1.0.
Richard> I believe that my problem is the same as for this patch,
Richard> except a whole lot worse. There are times that all my
Richard> windows freeze with everything blank when my mouse is near
Richard> the screen edges. I also have the problem that
Richard> EdgeResistance sometimes does not work but switches screens
Richard> when the mouse is just getting to the edge, but then not
Richard> redrawing the screen for a long wait.
Your problem may be related to that patch, but may also be partly
caused by an overworked system. I know if something is churning away
on my machine, I'll see long delays in switching pages with symptoms
like what you describe.
Richard> The question I have is, how to you apply this patch? I have
Richard> a Sun OS 4.1.3 system. I have never delt with patches
Richard> before.
See the FAQ, question #24:
----------------------------------------------------------------------
24) How do I create/submit/apply patches?
A: Creating a patch -
1) Copy the originial source file(s) to the same name with the
additional extension of .orig (or something like that).
2) Then run diff with either the -c (context) or -u (unified)
switch on the sets of files, with the .orig file FIRST. I
prefer unifified diff's because they are smaller, but
sometimes they aren't as readable, so either context or
unified diffs are fine.
ex: cp fvwm.c fvwm.c.orig ; diff -u fvwm.c.orig fvwm.c
Submitting a patch -
Just mail it to the fvwm mailing list, is the best way I
guess.
Applying a patch -
Get a copy of the program 'patch' from your favorite source,
such as prep.ai.mit.edu in /pub/gnu, compile it, and then
follow it's directions (generally just cd into the appropriate
directory and run 'patch < patchfile').
----------------------------------------------------------------------
Chuck
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Thu Jul 18 1996 - 08:00:29 BST