> The reason why some people have this problem is that it will most
> likely give you the correct behavior on PseudoColor visuals, while it
> will it will probably give you incorrect results on a TrueColor
> visual, since for PseudoColor it works on the colormap entries while
> for TrueColor it works on the color bits so you need to give it a
> pretty high number (I use XORValue 65535, mostly 1s).
If you use M4 preprocessing (and you should! :-) then use this handy macro.
It works for me on our Sun's, some of which have multiple heads, each
at different bits-per-pixel:
# XORValue -- this is the value that bits are XOR'd with when rubberbanding.
# If we have an 8-bit display, use 1, otherwise use 255. The default is '1',
# but it doesn't work well on deeper displays.
m4_ifelse(PLANES,`8',`
XORValue 1',`
XORValue 255')
Since fvwm2 starts a copy of itself for each display (which I think is
terribly wasteful of system resources; other window managers [vtwm, ctwm]
don't do this... and it is not just fvwm which gets spawned twice...
its FvwmAuto, FvwmButtons, FvwmIconMan, etc... yuck.) and parses the
.fvwm2rc for each display, this works great.
Obviously if those XORValues don't work for you (or you don't like them) you
can change them.
While I'm writing:
I *CANNOT* get the Decor-switching pop-up menu to work that lar3ry gensch
submitted (in the "decor_examples" file in fvwm-2.0.45, in sample.fvwmrc).
I tried it yesterday, and if I include a line like
Style "*" UseDecor Mwm
It works fine. But if I try to use the "decor switching" routines, fvwm
2.0.45 gets totally confused, placing the left, bottom and right handles
all in the upper left hand corner of the border, and completely locking
up the machine if you window shade a window in that state. Doesn't make
me feel to good.
Finally, am I missing something, or is adding buttons to the title bar
much more difficult in 2.0.45? I used to be able to add a line like
this:
ButtonStyle 6 12 50x10_at_1 25x35_at_1 40x35_at_1 40x60_at_1 25x60_at_1 50x85_at_1 75x60_at_0 60x60_at_0 60x35_at_0 75x35_at_0 50x10_at_0 50x10_at_1
to my .fvwm2rc file and it would appear in the title bar. But now, it is
happily ignored. I've tried resetting the button style, reset button 1 2
and 4, defining buttons 1 2 and 4, adding the 'vector' keyword, adding
'Style "*" Button 6', etc. all to no avail. How do you add a button to the
title bar if that is all you want to do?
Eddy
P.S. FvwmScript (in the 'extras' directory) blows away the FvwmForm module
in terms of capability (at the expense of requiring an external 'script'
file instead of being able to include it in your .fvwm2rc file). I have
been using FvwmScript for about a week now, and have made about 7 or 8
changes to the source, including upping the maximum number of widgets
from 30 to 100 to accomodate some dialog boxes I am working on. The
language is a little tedious, but it works great. I really should send
the changes in to the author so I can distribute my scripts... also,
we should consider having the name changed from FvwmScript to FvwmDialog,
which in my opinion is a much better name. :-)
--
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 Wed Jan 29 1997 - 12:00:21 GMT