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

Wine is tiled if not fullscreen #119

Closed
4n0nct opened this issue Sep 15, 2021 · 4 comments
Closed

Wine is tiled if not fullscreen #119

4n0nct opened this issue Sep 15, 2021 · 4 comments

Comments

@4n0nct
Copy link

4n0nct commented Sep 15, 2021

1/ It happens also with popups which are here to prelaunch a game, it will tile.
Imagine that tiny windows which just make you select a res and vsync, it should be really tiny, but then it will take all the screen, and making it "float" on the fly won't make it take its real size, it will still occupy all the screen.
wine and wineserver are in the ignored_list.

2/ After a game at low resolution is terminated, if the desktop doesn't return to its real resolution (it happens a lot), when I make a
xrandr -s 1920x1080
then the windows (for exemple: terminals) are not tiled anymore but floating.

3/ In the UI options there is a setting with a lot of 2,2,2,2,2,2,2,2,2,2,2,2,2,2
Will you clarify that ? I just don't understand what I'm looking at and how to interact and what it does

Thank you for your future answers.

@4n0nct
Copy link
Author

4n0nct commented Sep 15, 2021

In fact, the list doesn't work, everything is tiled automatically

@lingtjien
Copy link
Owner

lingtjien commented Sep 15, 2021

  1. You can ignore clients by expanding the ignored name regex (or caption) so that they are never tiled. In order to find the correct name of the client that you want to ignore you could open the client menu and then More Actions -> configure special application settings and in the window class box you'll find the name that you need to match with the regex
  2. What happens if you use the global shortcut Grid-Tiling: Refresh?
  3. See Confusing config #115 (but I'll add some more explanation in the readme next time)

@4n0nct
Copy link
Author

4n0nct commented Sep 21, 2021

Oh thx, didn't see you've answered, I will look at that.

@lingtjien
Copy link
Owner

Assuming, it's fixed by now. Otherwise you can open a new ticket 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants