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

Geometry doesn't take the invisible window border into consideration #633

Open
Sneakpeakcss opened this issue Jan 4, 2024 · 2 comments
Open
Assignees

Comments

@Sneakpeakcss
Copy link
Collaborator

Describe the bug

Using --geometry=0:0 moves it properly into a corner, but there's still a slight gap (probably the same issue as this).
In comparison, mpv seems to have a built-in solution for this. However, for me mpv doesn't seem to take the titlebar into consideration and basically positions the window like it's in set border no mode, while mpv.net only has the problem with left/right/bottom sides.

To Reproduce
mpvnet.exe --geometry=0:0
mpv.exe --geometry=0:0

Expected behavior
Geometry should move the player area completely into the corner, omiting the invisible border.

Screenshots
Same as in stackoverflow link

Additional context

  1. mpv.net version: mpv.net 7.0.0.5 (28.12.2023)
  2. Windows version WIN10 22H2
  3. GPU name RX570
@stax76
Copy link
Collaborator

stax76 commented Jan 4, 2024

It works on Windows 11. I find window related features rather difficult to do, so might not fix this.

mpv shows the title bar out of screen bounds, which is even uglier than the mpv.net issue.

Screenshot (8)

@Sneakpeakcss
Copy link
Collaborator Author

Sneakpeakcss commented Jan 4, 2024

It works on Windows 11. I find window related features rather difficult to do, so might not fix this.

To some extent i can relate, i've had similar problems when i was meddling with window positioning in AHK.

On the other hand, Alt+Arrow keys are somewhat working properly when it comes to positioning at the corners, but that probably uses an unrelated method of handling this.

And the "somewhat" part meaning that it has problems handling secondary monitors that are in lower resolution, basically improperly detecting the top/bottom bounds, making the "bottom" start in the middle of the screen, and Alt+BS moving it to the somewhat-off-center primary monitor. Works 100% fine on primary though.

mpv shows the title bar out of screen bounds, which is even uglier than the mpv.net issue.

Certainly agree on that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants