Describe the bug
When I retrieve the current display mode by initializing the display API before kinc_init and try to then open a window under wayland using that information, I get a window that is larger by the scaling factor I have set in my Window Manager (SwayWM) with scaled pixels.
To Reproduce
Steps to reproduce the behavior:
Use Linux+Wayland+Sway
Set the "Scale Factor" to something larger than 1
Run any sample like EmptyKinc and compare the window size to the expected window size (requires toggling the window to floating mode)
the window is "Scale Factor" larger than the specified dimension in Kinc
Expected behavior
Get a framebuffer with native resolution, regardless of the user set "Scale Factor"
Execution Environment:
Host system (where you compile your code): Linux
Target system (where you run your code): Linux+Wayland+SwayWM
IDE and/or compiler used: vscode
Kinc revision: ac733f5e
Kinc build output: the usual.. not important to the issue
Application output (if it runs): not important to the issue
Describe the bug When I retrieve the current display mode by initializing the display API before kinc_init and try to then open a window under wayland using that information, I get a window that is larger by the scaling factor I have set in my Window Manager (SwayWM) with scaled pixels.
To Reproduce Steps to reproduce the behavior:
Expected behavior Get a framebuffer with native resolution, regardless of the user set "Scale Factor"
Execution Environment: