On Fri, 29 Jul 2005, Etan Reisner wrote: > I was going to say that I'll bet this change was the problem: > > Fri May 27 09:38:20 EDT 2005 Tuomo Valkonen <[EMAIL PROTECTED]> > * Ignore _NET_ACTIVE_WINDOW request by default. > - Can be enabled by setting the ignore_net_active_window winprop to > false. > > but the version you said you were running before seems like it should > have been tagged after that change went it. I would see if setting the > winprop for the windows you are testing with "fixes" the problem.
I think the previous version must have been before ion-3ds-20050607 since this does fix it. (I overwrote my previous Ion binary before I realised something was different and tried to reconstruct what version it was from my last-but-one Ion download record.) Many, many thanks for the incredibly quick response. > P.S. _NET_ACTIVE_WINDOW is really a hint and the window manager is more > than free to ignore the request, so it's generally not so nice to assume > it will have worked and proceed, and unless there's a really good reason > I'd leave the mouse alone, apps moving the mouse whenever they want can > get pretty annoying. I remember an e-mail talking about this with Tuomo and I'm sort of the "reverse side of the coin" viewpoint: IMO one goal of a "tiling-style" window manager ought to be to provide a common tiling & window manipulation level common & accessible to all applications which allows them to make reasonable high-level requests of it like "the user has indicated they want to look at content that happens to be in window X, so please make sure window X is visible" and that by default requests should be honoured, but I certainly agree with you that it should be possible for the user to "blacklist" applications which they think abuse the facility. Without pushing this "requests into common tiling layer" idea you get N different applications with N subtly different tabbed sub-window implementations (eg, mozilla, kdevelop, gedit, ...) rather than a single, consistent one. My particular application is a sort-of editor which both uses the mouse extensively and opens a full X window for each open file, and the hint is used so things like clicking on a line of gcc error output brings up the appropriate window for the file, so I think it's a reasonable decision here to do the mouse warping. -- __cheers, dave____________________________________________ homepages.inf.ed.ac.uk/dtweed/ tel: +44 131 651 3447 JCMB, Kings Buildings, Edinburgh fax: +44 131 651 3435 X wrote a book about this, which Y was carrying around for a long time with little discernible effect -- John Baez
