@gavin67890 said in Display Module 13.2 issues:
I'm actually a little curious to see what this module does. There appears to be a separate UI, which maybe needs to be directly specified, rather than a mirror of the Core2 screen.
I think this may be the disconnect here. My understanding is the same, that the display module isnt something that just mirrors the device's screen to an external hdmi monitor.
It is (I am fairly sure) like the LCD unit, it just provides another, external screen space for you to draw in. You have to manually (via code) draw whatever you want on -that- screen/display, in code. It doesnt automatically duplicate what is on the main core lcd screen. the UIFlow demo app / setup menus arent going to appear on the HDMI display just because they appeared on the main LCD.
Although it -would- be a cool "requested feature" to have some sort of config/setup toggle to choose a display module as the "default screen" at boot - but then you would run into other issues, like.. how would you interact with the UIflow startup menus/network config/demos etc? There is no default "mouse driver" - even if you had the USB module as well. You would lose the touch interface unless you wrote your own.
And there you go, a new m5stack product request! - A combo HDMI display + USB mouse module with minimal driver to handle mouse movements and button clicks, a background task to continually update the position of a visibile mouse cursor, and if all present at boot time, just default to that display, and process those mouseclicks the same as touch input events. Assuming the USB module can handle HID devices, and not just filesystem devices/thumb drives, that should be an easy peasy piece of code-cake even with existing HW. Get on it, M5stack!
And clearly Ive had too much caffeine and should stop babbling.