Tim Hanson <tjhanson_at_attbi.com> wrote:
>> On Sat, Apr 20, 2002 at 10:52:15PM -0700, Tim Hanson wrote:
>>
>>>I switched to SuSE 8.0 a while back, on a number of computers. For some reason
>>>I can't Swallow programs like xeyes and asclock anymore. Is there a fix?
>*FvwmButtons (2x2 Frame 0 Swallow(UseOld) "FvwmPager" "Module FvwmPager 0 0")
>*FvwmButtons (3x2 Swallow "xosview" `Exec xosview`)
>*FvwmButtons - - Swallow "FvwmXeyes" Exec xeyes -name "FvwmXeyes" -geometry +0+0
>-bg grey67 &
FvwmButtons seems to be _very_ sensitive to a number of things,
and the results are always odd. I'll use your xeyes command as
an example and show how to trouble shoot this kind of problem.
(This pretty much describes what I actually did, too.)
First, look at the obvious differences in the command you using
for that one and the commands for others that do work. Instead
of the above, try this,
*FvwmButtons (- - Swallow "FvwmXeyes" \
Exec xeyes -name "FvwmXeyes" -geometry +0+0 -bg grey67 &)
Opps, that doesn't work either. So lets cut it down to a bare
minimum and see what happens,
*FvwmButtons (- - Swallow "FvwmXeyes" Exec xeyes &)
Hmmm... still won't work, so:
*FvwmButtons (- - Swallow "FvwmXeyes" 'Exec xeyes &')
It _still_ doesn't work! (This one is tricky, and not at
all obvious.) Run xeyes from the command line and then run
xwininfo on it. The first line of information is,
xwininfo: Window id: 0xa00007 "xeyes"
The problem is that FvmwButtons knows to grab this process by
the window id name, and if it doesn't match... it doesn't work.
*FvwmButtons (- - Swallow "xeyes" 'Exec xeyes &')
Bingo, that one works! (It will also work if the "&" is removed
too.) So then you can try putting your customizations back in.
The first discovery is that there is no point in using the
-geometry option, it's ignored anyway.
I'm not sure what the -name option will do with your
configuration. On mine it causes a name to be put in the title
bar, which causes xeyes to not be swallowed correctly (but my
overall configuration tells fvwm not to decorate xeyes, so it
may be different for your config).
Another odd point is that setting the background won't do
anything unless the +shape option is also used.
So that ends up with a line that looks like
*FvwmButtons (- - Swallow "xeyes" 'Exec xeyes -bg grey67 +shape')
You can apply the same process to the others and eventually get
them to work too.
1) Start with the most basic command you can, just to get
it to "work".
A) Copy the syntax used in a functioning example.
B) Determine the actual window name by running
the program and invoking xwininfo.
2) Add other options such as framing, padding, and/or
3) Add other program options, such as -bg. This may
need to be coordinated with 2) above.
Note that when something causes a problem, it might have
almost any manifestation, and generally it is exceedingly
difficult to connect what happens to what might have caused
it. Hence stick with making exactly one change at a time,
using "killall FvwmButtons" to kill the module and then
restarting it from within fvwm each time (you don't have to
kill fvwm itself each time).
--
Floyd L. Davidson <http://www.ptialaska.net/~floyd>
Ukpeagvik (Barrow, Alaska) "Place where people hunt snowy owls"
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sat Oct 12 2002 - 16:38:33 BST