Thomas Adam <tho...@fvwm.org> writes: > On 15 January 2013 18:41, Dan Espen <des...@verizon.net> wrote: >> Thomas Adam <tho...@fvwm.org> writes: >> >>> On 15 January 2013 10:32, Pierre Frenkiel <pierre.frenk...@gmail.com> wrote: >>>> hi everynody, >>>> I have a lot of "style" settings, and up to now all worked perfwctly. >>>> Today, I added a line for xzoom >>>> >>>> Style "xzoom" NoTitle, NoHandles, Sticky >>>> >>>> but these settings are ignored for all xzoom windows. >>>> >>>> Any idea? >>> >>> What does FvwmIdent tell you about the name/class/resource of such a window? >> >> If I recall, 2 things can cause a bad style match, > > Three; you missed one. :P > >> first, as you suggest, the windows may not have an intuitive >> name/class/resource. >> That we can see with FvwmIdent. >> >> The other is that the window is created with some other name and then >> gets it's name/class/resource later. I forget how we diagnose that, >> is it FvwmDebug? > > BugOpts DisplayNewWindowNames
Duh. Looked at BugOpts twice, and here it says: "This can help in finding the correct strings to use in the Style command." Talk about needing a page magnifier. > Note that a window's class cannot be changed once the window is > mapped; only in the WithDrawn state. I've mentioned this a few times > before on this list; only one or two GTK apps that I know of decide to > change their title after the window has been mapped; transitioning > from FVWM's default of "NoName" to something else -- but that won't be > what's happening with XZoom. > > The third one is that style line ordering matters a great deal in the > config file. Well, yeah, but... -- Dan Espen
