>>> Dan> drag and drag and it won't switch pages. If I then hit Control-right,
>>> Dan> it works fine, and thereafter edgescroll works normally. I'm not sure
> >
> > I have to click on a different virtual desktop on the pager, and then
> > edgescroll starts working again, and seems to keep working until I restart
>
> and 43. If you need to check out an fvwm2rc to duplicate this, check out
> http://dosa.ini.cmu.edu/~manojk/fvwm2rc
Using this .fvwm2rc file I was able to duplicate this error. It
does NOT happen with my .fvwm2rc file. I'm currently eliminating things
to see if I can narrow down what causes the error.
While doing all this I thought I'd mention some things I noticed:
there is an error in the fvwm2 man page: "fvwm2 -f" is now "fvwm2 -cmd" and
the man page should reflect that. :) Also, I like how the failsafe mode
works now. You get one menu with quit on it. Perhaps it should pop up a
menu box and say that the .fvwm2rc file was not found?
Ok... after playing around for about a half hour, I think I have
an idea about what is going wrong. I suspect that everyone who encouters
this problem uses FvwmCpp.
When I got the above listed .fvwm2rc file I had to switch to
starting Fvwm with FvwmCpp. As soon as I did that, I was unable to switch
virtual screens. I winnowed away at the .fvwmrc file until I had only this:
In my .xsession: exec fvwm2 -cmd "FvwmCpp /home/staff/eburke/.fvwm2rc"
----------------cut--------------------------
ModulePath /usr/lib/X11/fvwm2/
HilightColor linen SteelBlue4
AddToFunc "InitFunction"
+ "I" Module FvwmPager 0 0
AddToFunc "RestartFunction"
+ "I" Module FvwmPager 0 0
AddToMenu "Utilities" "Utilities" Title
+ "Exit Fvwm" Popup Quit-Verify
AddToMenu "Quit-Verify" "Really Quit Fvwm?" Title
+ "Yes, Really Quit" Quit
+ "Restart fvwm" Restart fvwm2
Mouse 1 R A Menu Utilities Nop
----------------cut--------------------------
The shortest possible fvwm2rc file that doesn't fail. And each time
I restarted I still had trouble. Then, switching my startup back so that it
does NOT use FvwmCPP caused the problem to vanish.
I would have tried running my normal .fvwm2rc through FvwmCpp as a
backup test, but it barfs on it for some reason and gives me the failsafe.
So this doesn't exactly solve the problem but it should help
pinpoint it somewhat. Anyone care to tell us if FvwmM4 has a similar
problem?
--
Eli Burke
eburke_at_csugrad.cs.vt.edu
http://csugrad.cs.vt.edu/~eburke/
--
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 Mon Jul 15 1996 - 14:50:15 BST