You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
My setup is dual monitor and I noticed:
When in full session, cassowary tries automatically to go fullscreen but it maps both monitors and the virtual machine's resolution is set as the rectangle containing both displays. The leftmost monitor works but the image is cropped to it's resolution and the rightmost glitches between showing the full image and showing the login wallpaper
When running an app and dragging it to the top to make it fullscreen, the image grows on both screen, in the same way as said before and both displays glitch.
To Reproduce
Launch any app on multiple monitor setup and make it fullscreen or launch full rdp session.
Expected behavior
The app should fill only one display, same for the rdp session (at least until multi-monitor is supported)
Screenshots
This is opening an app, I'm not able to show the full session screenshot as I can't open the hosts screenshot utility when running.
System information:
Cassowary Linux client version: 0.6A
Cassowary windows component version: 0.6A
Linux Distribution: openSUSE Tumbleweed 20230717, KDE Plasma 5.27.6, wayland
Windows/Edition used: Windows 10 Pro
Additional context
Great work on the app!! Thanks a lot for sharing.
The text was updated successfully, but these errors were encountered:
Describe the bug
My setup is dual monitor and I noticed:
To Reproduce
Launch any app on multiple monitor setup and make it fullscreen or launch full rdp session.
Expected behavior
The app should fill only one display, same for the rdp session (at least until multi-monitor is supported)
Screenshots
This is opening an app, I'm not able to show the full session screenshot as I can't open the hosts screenshot utility when running.
System information:
Additional context
Great work on the app!! Thanks a lot for sharing.
The text was updated successfully, but these errors were encountered: