Ubuntu

Bug #38753
Comment #55

Comment 55 for bug 38753

Revision history for this message

In KDE Bug Tracking System #36065, Get-sonic (get-sonic) wrote on 2016-03-03:

#55

(In reply to Martin Gräßlin from comment #47)
> (In reply to Syam from comment #46)
> > The problem is that this raise happens not on 'click' but on mouse-down
> > itself.
>
> This is correct, the raise happens on press if that's the action you
> configured for what happens on click on inactive window. This is
> configurable. If you don't like the default of "Activate, Raise & Pass
> Click" change it to "Activate & Pass Click".

This has been suggested earlier. But it doesn't really work, because the setting is really for mouse-down and not a 'click' (which is completed at mouse-up). With "Activate and Pass click", the window won't be raised after one click. The user needs to click on it again to raise it. And that is indeed weird, I agree.

>
> Changing the action to be performed on release instead of press would be
> rather weird. The window would not activate till you release. That's not
> what a user (and applications) expects.

Is it really weird? I wonder how it is done on Windows? Does the background window raise at mouse-down itself or only on 'click', i.e. after mouse-up? I have to boot in to a Windows machine before confirming.

> If we had any chance to know that
> the user intends to drag we could perform a different strategy.
I see from some earlier comments that the devs are stuck on this 'angle' to solve the problem. But as mentioned in the original report, 'raising at mouse-up and not immediately after mouse-down' would solve it without any need to know if a drag is being done.

>
> To me the issue is fixed. This bug report contains multiple suggestions on
> how it should behave. Several of them even contradicting.

Well, the original report mentions one problem and one solution. I understand that it is difficult to implement this with current technology - as pointed out in some earlier comment, on current Linux desktops & GUI libraries, everything seems to happen at mouse-down and not on mouse-clicks.

>
> Now as I'm the only one here who probably has tried this out, I ask you to
> first try it before starting discussions about the state of this bug report.

I am deeply sorry if my earlier comment offended you. I was afraid if it'd come out like this. But I didn't mean any disrespect. I have very high regards for devs, especially you :-)

(In reply to Martin Gräßlin from comment #47)
> (In reply to Syam from comment #46)
> > The problem is that this raise happens not on 'click' but on mouse-down
> > itself.
> 
> This is correct, the raise happens on press if that's the action you
> configured for what happens on click on inactive window. This is
> configurable. If you don't like the default of "Activate, Raise & Pass
> Click" change it to "Activate & Pass Click".

> 
> Changing the action to be performed on release instead of press would be
> rather weird. The window would not activate till you release. That's not
> what a user (and applications) expects.

> 
> To me the issue is fixed. This bug report contains multiple suggestions on
> how it should behave. Several of them even contradicting.

> 
> Now as I'm the only one here who probably has tried this out, I ask you to
> first try it before starting discussions about the state of this bug report.

I am deeply sorry if my earlier comment offended you. I was afraid if it'd come out like this. But I didn't mean any disrespect. I have very high regards for devs, especially you :-)