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
if monitor is connected during the boot to the device, headless-kivy reads monitor resolution but it wants to broadcast it to the 240x240 display. We can force the resolution to 240x240 for ubo pod but allow developers to change this with a flag to get the resolution from upstream.
I can connect the monitor after the app loads and GUI is displayed on the device LCD screen and use the monitor (terminal) without issue.
Previously (I believe version 0.15.2 or prior) the GUI was displayed on the monitor if monitor was connected during app startup but I guess the recent change it headless kivy broke / changed that behaviour. I believe this is related to this change in headless-kivy library.
I guess forcing the resolution is going to give us the ideal behavior.
The text was updated successfully, but these errors were encountered:
if monitor is connected during the boot to the device,
headless-kivy
reads monitor resolution but it wants to broadcast it to the 240x240 display. We can force the resolution to 240x240 for ubo pod but allow developers to change this with a flag to get the resolution from upstream.I can connect the monitor after the app loads and GUI is displayed on the device LCD screen and use the monitor (terminal) without issue.
Previously (I believe version
0.15.2
or prior) the GUI was displayed on the monitor if monitor was connected during app startup but I guess the recent change it headless kivy broke / changed that behaviour. I believe this is related to this change inheadless-kivy
library.I guess forcing the resolution is going to give us the ideal behavior.
The text was updated successfully, but these errors were encountered: