On Wed, Oct 08, 2008 at 10:59:01AM -0400, Tom Panning wrote: > On Tue, Oct 7, 2008 at 6:36 PM, Rhialto <[EMAIL PROTECTED]> wrote: > > On Tue 07 Oct 2008 at 18:36:42 +0100, Thomas Adam wrote: > >> 2008/10/7 Tom Panning <[EMAIL PROTECTED]>: > >> > I'm not very familiar with fvwm, but I'm trying to find a window > >> > manager that will raise all of the windows in a window group > >> > together. > > > >> Pick All ($[w.class], !Transient, CurrentPage) RaiseLower > >> > >> Other conditionals you might want notwithstanding in this example. > > Thomas, thanks for this. It gave me a huge push in the right direction, > but see below. > > > Do all windows in one window group (assuming a window group means they > > share a WM_CLIENT_LEADER(WINDOW)) also share the class? > > I hadn't seen the WM_CLIENT_LEADER property. I was looking at the > WM_HINTS window_group field. It appears that, for the applications that I'm > interested in, the WM_CLIENT_LEADER property works just as well. However, > the class is not quite as good because two separately launched instances of > the > same application will have the same class but shouldn't be in the same > "group". > > Thanks, > Tom
If you don't mind picking up another module, FvwmProxy lets you group windows by including on patterns (name, class, or resource) and optionallly pick up anything with the same client leader (or process). The process/client check can also exclude the like-named patterns of other processes. Manual grouping can be done by matching colors on the proxy windows. Grouped windows raise and lower together. You can also stick window borders together or "isolate" groups so that their windows are co-located and only one is unhidden at a time (like Firefox tabs). All that is secondary to the proxy navigation feature. -- Jason Weber
