Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wayland window switching does not completely focus on the application upon Alt+Tab and middle click. #513

Closed
unsafeunaudited opened this issue Jan 29, 2024 · 3 comments

Comments

@unsafeunaudited
Copy link

unsafeunaudited commented Jan 29, 2024

Describe the bug. What happened?

Coming from the OS file explorer, If I Alt+Tab into Weasis and if my first interaction is to adjust the windowing and leveling (that I've bound to the middle click), the keyboard does not completely transfer to Weasis. So if I press D to do a distance measurement, Weasis does not recognize that I've pressed the button and just does a drag to highlight function instead. This also noticeable when I try to close the current active patient/image with Ctrl+W shortcut. Oftentimes nothing happens and sometimes the prior used application (like the explorer) gets closed instead.

As a temporary measure, I double click the current active patient/window to make it go full screen and press Esc to return back to the normal viewing mode. Only then do Weasis get proper focus and recognizes the keyboard shortcuts.

What version of Weasis are you running?

4.2.1

On which system the problem occurs?

Linux

Relevant log output

none

Additional contextual elements

Wayland <-- broken
X11 <-- normal/no issue
GNOME
Fedora 39
.rpm installer
AMD GPU

@nroduit
Copy link
Owner

nroduit commented Jan 29, 2024

I've tested a Wayland session with Ubuntu and I don't see these problems.

I have the impression that these problems are linked to the distribution and its management of Wayland. There's another issue with Fedora.

@nroduit
Copy link
Owner

nroduit commented Feb 24, 2024

You can try with

@nroduit
Copy link
Owner

nroduit commented Jul 27, 2024

We're closing this issue due to inactivity over the past several months. If the problem persists or if you have any further information to provide, please feel free to reopen this issue or create a new one.
We appreciate your contributions and feedback!

@nroduit nroduit closed this as completed Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants