You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going between GNOME Shell 46.0 and XFCE 4.18. XFCE is running on 0.7.2 bin at the moment, where as my Ubuntu machine is compiled from source (however switching to a precompiled binary the behaviour is still the same).
I'm able to go to either desktop fine, but it requires a key-press release each time to get back to GNOME. I would like to get to a state of just being able to move to either monitor without this. Would just like to validate if this just a current limitation at the moment, or something I need to fix elsewhere.
I did find similar issues (#94) but these appeared fixed in newer versions so assumed its something I'm doing or I am just misinterpreting the behavior.
Best!
The text was updated successfully, but these errors were encountered:
Xfce needs X11 input capture to be able to recognize when the pointer leaves the screen, which is not yet implemented. So this is expected at the moment.
Thanks for replying @feschber and for the heads up. Is it worth having a matrix or something similar in the README of current limitations between desktops? I think in my naivety coming from barrier that the behavior is somewhat ingrained into my head. Obviously hopping between different desktop APIs is going to encompass a number of challenges that might need to be spelled out to dummies like myself :')
Going between GNOME Shell 46.0 and XFCE 4.18. XFCE is running on 0.7.2 bin at the moment, where as my Ubuntu machine is compiled from source (however switching to a precompiled binary the behaviour is still the same).
I'm able to go to either desktop fine, but it requires a key-press release each time to get back to GNOME. I would like to get to a state of just being able to move to either monitor without this. Would just like to validate if this just a current limitation at the moment, or something I need to fix elsewhere.
I did find similar issues (#94) but these appeared fixed in newer versions so assumed its something I'm doing or I am just misinterpreting the behavior.
Best!
The text was updated successfully, but these errors were encountered: