At first I found this whole discussion pretty annoying, but I have to
complement some of you for some interesting discussion of this topic.
I hope I am contributing a new viewpoint on this...
We haven't heard from Chuck, but my guess is there is no way fvwm2
would change its default focus policy. The "sample.fvwmrc" that comes
with fvwm2, already assumes a default focus policy and supplies
overrides of clicktofocus for:
FvwmButtons, xbiff, Maker, Appointment, xcalc, xman, xvgr, matlab,
xmag, xgraph, sppeed6, and xmosaic.
Any change to the default would break every .fvwm2rc file around. I
would hope that we would worry more about the existing fvwm2 user base
than some new users. I think this viewpoint is more significant than
which policy is the better default. I, for one, would feel compelled
to change the source code before installation, if this change was
actually made.
My guess is that a POLITE request from the metacard people for
metacard to be added to the the clicktofocus list in the
"sample.fvwmrc", might be granted. Although the arguments that
metacard should attempt to get their application to work smoothly
under any focus policy seem pretty compelling.
--
Dan Espen Phone: (908) 699-5570
dane_at_bae.bellcore.com
444 Hoes Lane Room RRC 1C-214
Piscataway, NJ 08854
--
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 Oct 24 1996 - 08:57:51 BST