>> On Mon, 22 Apr 1996 16:58:43 -0400,
>> Dave Goldberg(dg) wrote:
dg> For what it's worth, I also run xbuffy swallowed in the buttons, have
dg> Style "*" DecorateTransients set, run with Henrique's patch (and some
dg> others), but do not see the problem behavior. My xbuffy popups still
dg> come up undecorated, as they should.
dg> Style "XBuffy" NoHandles, NoTitle
aye, there's the rub. Thanks for jumping in Dave.
Identify reports the Name, Icon Name, and Resource as "xbuffy", but
the Class as "XBuffy". When I made the change to use the Class name,
as you do, it works for me, too. Although the man page says,
windowname can be a window's name, class, or resource
string.
it appears to only work if the class is used for the windowname. Can
anyone else confirm this?
I was only able to duplicate the breakage from a fresh start of fvwm
using "xbuffy" as a windowname; I wasn't quite sure how to clear a
style using FvwmTalk.
If someone else can confirm this, is this change intentional? It
doesn't really matter as far as I'm concerned -- I just need to be
clear as to what the rules of the game are.
dg> *FvwmButtons(26x1, Frame 0, Padding 0 0, Container(Frame 1, Padding 0 0 Rows 1))
dg> *FvwmButtons(Swallow(Kill) XBuffy "Exec xcmd xbuffy")
I've just been using the old syntax; I'll have to try this newfangled
Container stuff soon.
--
-mb-
--
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 Apr 22 1996 - 16:39:43 BST