Loading...
  OR  Zero-K Name:    Password:   

Borderless Window Offset Issue

10 posts, 1228 views
Post comment
Filter:    Player:  
sort
Borderless Window is incorrectly aligned with the following steps (on a 1920x1080 monitor):

With a fresh install, Borderless is chosen by default. springsettings.cfg does not have parameters XResolutionWindowed or YResolutionWindowed. Everything looks correct ingame so far.

[This step is not necessary to reproduce the error, but it is still interesting] If I set window to Fullscreen, enter and quit game, and then set window back to Borderless, enter and quit game, springsettings.cfg now has parameters XResolutionWindowed - 1920 and YResolutionWindowed - 1080. This still looks correct in game, but it is interesting that Borderless adds these parameters when they were not in springsettings.cfg initially.

If I set window to Windowed, enter and quit game, springsettings.cfg adds parameters XResolutionWindowed and YResolutionWindowed if they don't already exist, and sets them to 1916 and 1053, respectively. If I then set window to Borderless, enter and quit game, XResolutionWindowed and YResolutionWindowed do not change back to 1920 and 1080, respectively. This causes the game screen to be slightly offset, which allows the player to click outside the game. Either changing these parameters back to 1920 and 1080, or deleting these parameters, solves the problem.

By the way, for things like this, should I post them here, or on the dev website?
+1 / -0
Recently switched over from fullscreen to borderless and I had the same issue.
+1 / -0
If resoulution was set to 1916x1053 or 640x480 or anything you prefer in springsettings.cfg then it is good that engine doesn't arbitrary resets it.
Does one really need to switch between borderless/windowed/fullscreen modes? It's more like one time configure option.

a) Fullscreen doesn't require manually set resolution.
b) Borderless and windowed requires resolution parameters.
Borderless is the same mode as windowed except it doesn't have borders.
So what's the issue?

If you want the engine to autoreset resolution - then it's a feature request (additional param in springsettings that tracks if res was auto-set or something like that, useless imho)

EDIT: Probably i misunderstand original OP. Were you talking about switching modes in ZKL and that ZKL actually sets those params and doesn't resets them?
+0 / -0
9 years ago
Yes, I am talking about switching modes in ZKL, and then ZKL setting these params itself. When I choose Borderless, ZKL should change XResolutionWindowed and YResolutionWindowed to the desktop resolution in order to appear like fullscreen, but instead, it keeps these parameters unchanged.
+0 / -0


9 years ago
Please go to adv. engine settings (custom settings) and delete offset values in ZKL
+0 / -0
9 years ago
Yeah, either changing the parameters back to 1920 and 1080 or deleting them solves the problem. I am just mentioning this issue because it seems like ZKL should make these changes if the user changes window mode to Borderless.
+0 / -0


9 years ago
UAranklamer: The point of Borderless Window is to basically have fullscreen without requiring a time-consuming context switch when alt-tabbing or clicking outside of the game space onto an additional monitor. If it doesn't fill the screen it's rather defeating the point.
+2 / -0

9 years ago
About borderless use-cases: faking fullscreen is not the only purpose, you can manually set smaller size (e.g. to monitor some background process with only 1 display) and use /grabinput + WindowPosX/Y in springsettings.cfg or alt+click to drag spring window anywhere you want (in kde).

Anyway I thought by mistake that Beamer was talking about engine. But he's right about usability issue in lobby, it should reset those values on window mode switch (because faking fullscreen is the most common case). Disregard my original post.
+0 / -0


9 years ago
Oh, right, Linux WMs let you move windows from any point, though alt+click does have a meaning in Spring and probably gets captured by it.
+0 / -0


9 years ago
quote:
though alt+click does have a meaning in Spring and probably gets captured by it.

You have to /grabinput for Alt to be received by spring. Otherwise, WM takes precedence.
+0 / -0