On Thu, 2008-04-17 at 16:40 +0100, Tim Cutts wrote: > Thanks for that way of looking for things. That's useful. The original > source of this bug report was a user of the program acedb > (http://www.acedb.org, if you really care!) This program creates a lot > of windows. In the version of GNOME supplied with sarge, the window > list grouped these windows nicely by database. Using the same xace > client, but upgrading the desktop to etch, broke this behaviour and the > window list sorts the windows alphabetically. > > OK, let's ignore my little tk script, and stick with acedb. > Fortunately, I used to use acedb, so I can reproduce what the user is > seeing. > > I can confirm that acedb is setting WM_CLIENT_LEADER correctly, and that > if I run two copies of acedb, each set of windows has a distinct value > of WM_CLIENT_LEADER. However, the window list still groups them all > together, and sorts the window names alphabetically, with no regard for > the value of WM_CLIENT_LEADER in the sort order. > > So there's definitely something wrong here. I will see if I can > duplicate the issue on a lenny machine.
Hi again, I gave it a try with acedb and the behaviour seems to be the same on etch and sid. If I run two processes of xace, each with several windows open, they are all grouped togheter. Just to make sure I don't misunderstand anything; You would prefer it if there were two groups, one for each xace process? Alternatively, it would be better if the group didn't sort the names alphabetically, instead making it clear which windows belonged to which process? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22
signature.asc
Description: This is a digitally signed message part
