Comment Re:No - that is changing focus (Score 1) 259
I see I misread what fnj wrote in my haste and excitement. Yes, it seems fnj is just describing sloppy focus behavior in E17. I misread "as soon as the mouse goes over it" as "as soon as the mouse button goes down over it".
Still, you're providing an excellent example of not getting it.
This is really easy: go find a computer with Windows or Mac OS and try it out, then try to do the same thing on anything built on X. Seriously, if you haven't once seen a properly functioning click-to-focus-unless-the-ButtonPress-could-begin-a-drag system, there's no point in replying.
There is no version of PointerRoot or sloppy focus or any such thing that exhibits the correct (as in, "expected by most of the world") behavior. Windows and Mac users—i.e. the vast majority of computer users—do not expect a window to get focus and stay below other windows as PointerRoot and sloppy focus allow. It has to be at least click-to-focus and raise-on-focus, or you're talking about a system that does not work as most people expect it to. All the systems have windows that are exceptions like docks, menu bars, palettes, the desktop; those are not the issue. Neither are pedantic points about scroll wheels being implemented as buttons 4 and 5.
The problem is that on X click-to-focus is click-to-focus-always. It needs to be click-to-focus-unless-some-conditions-are-met. One of those conditions is that the ButtonPress not possibly be the beginning of a drag; there may be other conditions I'm forgetting at the moment.
At least most of the people I've known to have worked on window managers acknowledge that they cannot do what Windows and Mac do without baroque schemes. I don't know who you are calling "bullshit" on behavior that has long been standard on Windows and Mac OS.
I've already wasted too much time on this. Until you've realized that there is a deficit in existing X-based systems, or found one that lacks the deficit, I'm not replying again.