On 01 May 2002 15:41:53 -0500, David A. Rogers wrote:
>
> I am running fvwm 2.4.6 on Linux Debian (testing/Woody). I have a few
> keys defined to be available in any context:
>
> Key F1 A M Popup PersonalMenu
> Key F5 A SC GoToPage 0 0
> Key F6 A SC GoToPage 1 0
> Key F7 A SC GoToPage 2 0
>
> Key F9 A SC Exec Eterm -g 90x50 -f white -P ~/pixmap/bhbkg.jpg_at_:tiled
>
>
> I also have a Buttonbar defined. So far it only has a clock and the pager in
> it. If it has xclock in it, the above keys work fine.
>
> *FvwmButtons: (Swallow XClock `Exec exec xclock -update 1 -padding 1`)
>
> If it has either dclock or asclock in it, the above global keys have no effect
> - until another application has been opened. After another application is
> open the keys again work fine. Even after the other application is closed.
> The keys still work fine.
>
> *FvwmButtons: (2x1, Swallow DClock `Exec exec dclock -slope 90 -bg black -led_off black`)
> or
> *FvwmButtons: (Swallow asclock `Exec exec asclock -12 -shape -geometry +3+3`)
>
> The only thing I can think of is that maybe dclock and asclock accept input
> and xclock doesn't. But I don't see what to do about it. By the way, this
> didn't happen with an earlier version of fvwm that I'm running at home (2.4.3
> I think).
>
> I can post my entire rc file if that would be helpful, but, as you may know,
> Debian has a standard setup for fvwm that provides hooks for users to fill in.
> So if you want to see the whole setup, you'll get a lot of stuff. I've gotta
> figure it's in this area though since the problem goes away if I use xclock
> instead of dclock.
>
> Any suggestions?
You may try "Style FvwmButtons NeverFocus", "Style asclock NeverFocus",
but I can't reproduce any problem myself with 2.4.x.
You may also try 2.5.1 and create minimal-rc showing the problem, put it
~/.in fvwm and run "fvwm -f minimal-rc".
Regards,
Mikhael.
--
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 Wed May 01 2002 - 17:29:46 BST