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

Setting runner width under wayland is unusable/impossible #287

Open
stefonarch opened this issue Jul 21, 2024 · 0 comments
Open

Setting runner width under wayland is unusable/impossible #287

stefonarch opened this issue Jul 21, 2024 · 0 comments

Comments

@stefonarch
Copy link
Member

Or better: any temptation to do so produces visual artefacts and ends up with garbage value like
width=174263 which results in a shown width which is the width of the smaller monitor (1280px here). An attempt on the smaller monitor to resize:

artefact-runner.mp4

Modifying with one monitor only:

resize-runner.mp4

The only way to get normal size and not 1280px is to

  • stop the runner module
  • edit or remove width setting in ~/.config/lxqt/lxqt-runner
  • needs even relogin eventually, especially with 2 monitors.

This is slightly different on different compositors, like on kwin the runner window can expand over both monitors when resizing, and on wayfire it can be be bigger than the monitor where it's shown.

Expected Behavior

Runner width can be configured under wayland.

Current Behavior

It's impossible and will result with runner taking the size of the smaller monitor.

Possible Solution

Fix the resize cursor movement effect which multiplicates apparently? This is the main cause.

Adding a limit for any width (only under wayland)? Default is 300px which can look to small on recent screens. Limit width to a third or a fifth of monitor size or to ?

Steps to Reproduce (for bugs)
  1. Try to resize runner window under wayland
System Information
  • Distribution & Version: arch, LXQt 2.*
  • Qt Version: 6.7.2
@stefonarch stefonarch moved this to Todo/Issues in Wayland Support Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo/Issues
Development

No branches or pull requests

1 participant