Review Request 113971: improve screenlocker multiscreen handling

[Thomas Lübking]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113971/#review44054
-----------------------------------------------------------



ksmserver/screenlocker/greeter/greeterapp.cpp
<http://git.reviewboard.kde.org/r/113971/#comment31580>

    this is just for me, since i do not intend to install a "screensaver".
    It shows a white window instead when set 1
    
    Can be dropped from final patch if there's no interest from other ppl.



ksmserver/screenlocker/greeter/greeterapp.cpp
<http://git.reviewboard.kde.org/r/113971/#comment31581>

    no idea why this was still there (probably my fault) but we filter the application, ie. get events for every widget and there was no smart filter juggling as well.
    
    -> removed because it just pollutes event forwarding (since we receive every keyboard event on this twice)



ksmserver/screenlocker/greeter/greeterapp.cpp
<http://git.reviewboard.kde.org/r/113971/#comment31582>

    this loop is required to make the qml/graphicsscene properly hadnle the forwarded events.



ksmserver/screenlocker/greeter/greeterapp.cpp
<http://git.reviewboard.kde.org/r/113971/#comment31583>

    the rest here searches for the window under the mouse, assumes that is where the focus shall go and passes it there.
    
    If the assumption is wrong, the only "problem" is that the lineedit is not focused (but due to event sharing you should see the input nevertheless)



ksmserver/screenlocker/greeter/greeterapp.cpp
<http://git.reviewboard.kde.org/r/113971/#comment31585>

    I twisted this check.
    The reason is that if you juggle the mouse, only the screensaver below will hide.
    
    So far the result was that the next keypress would hide the other screensavers and only the second next and following would be actual password input.
    
    Now the remaining screensavers are just kept intact and you operate on the only visible item.
    
    I assume that users will move the mouse until they see the greeter (if the first hidden screensaver was on a powered off screen) so this should be no issue (while the eaten second key kinda was to me)



ksmserver/screenlocker/greeter/greeterapp.cpp
<http://git.reviewboard.kde.org/r/113971/#comment31586>

    This is obviously very important.
    If we enter a recursion here, the user will not be able to enter a password on a multiscreen context


- Thomas Lübking


On Nov. 20, 2013, 4:52 p.m., Thomas Lübking wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/113971/
> -----------------------------------------------------------
> 
> (Updated Nov. 20, 2013, 4:52 p.m.)
> 
> 
> Review request for Plasma, Christoph Feck and Martin Gräßlin.
> 
> 
> Bugs: 311188
>     http://bugs.kde.org/show_bug.cgi?id=311188
> 
> 
> Repository: kde-workspace
> 
> 
> Description
> -------
> 
> - pass focus to greeter under the mouse
> - share keyboard events
> - let through keyboard events for one hidden locker
>   (mouse wakeup case)
> - remove double filtering
> 
> @Christoph:
> I meant a real human. A shared responsibility simply means that no one is responsible.
> 
> @Martin:
> I found the dupe and it's assigned to you. Do you feel in charge here or do you know whom to addd?
> 
> 
> Diffs
> -----
> 
>   ksmserver/screenlocker/greeter/greeterapp.h 951b1e3 
>   ksmserver/screenlocker/greeter/greeterapp.cpp bf33945 
> 
> Diff: http://git.reviewboard.kde.org/r/113971/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Thomas Lübking
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20131120/0533765d/attachment-0001.html>