gkoh
Improve the touch screen experience
As of v3.0.0-rc2, all devices are implemented with a text driven menu interface.
For touch screen devices like the M5Core2, this results in:
- smaller than necessary menu entries (which can be difficult to accurately touch)
- waster screen real estate
With the new LVGL graphics library, it should be relatively straightforward to modify most menus to be icon driven. If icons are laid out in a grid, use of screen can be maximised.
This will require some custom graphics for the icons, the stock symbols provided with LVGL are limited.
Furthermore, for shutter lock, implement:
- press and slide
This would replace the current 'long-press' shutter lock and could mirror the app (where there is only the shutter button, that can slide).
The core implementation with Symbols at the bottom of the screen to identify the function of the 3 buttons would be a good crossover point for enhancing the touch interface. With an up down and next button
The M5tough has no touch buttons, but having the 3 graphic buttons to navigate with by touch would still work
The graphics need to be a bit bigger though for those of us with big fingers, a nice square key
The touch to adjust times is too small, again dropping back to the 3 touch only buttons would improve this as you would be using the 3 square buttons only.
The core implementation with Symbols at the bottom of the screen to identify the function of the 3 buttons would be a good crossover point for enhancing the touch interface. With an up down and next button
The M5tough has no touch buttons, but having the 3 graphic buttons to navigate with by touch would still work
The graphics need to be a bit bigger though for those of us with big fingers, a nice square key
My original plan was to embrace the full touch experience, with everything driven by large buttons and very few (or zero) text driven menu systems. However, I am open to suggestion, or better yet, mock ups. The screen on all the touch devices is 320x240, so we can fit a reasonable amount on it.
The touch to adjust times is too small, again dropping back to the 3 touch only buttons would improve this as you would be using the 3 square buttons only.
@Grumpytech4 Could you elaborate on what 'touch to adjust times is too small' means?
When adjusting time values the touch area for each number to roll them up or down is too small and your finger covers the number you are changing so there is difficulty setting the values correctly.
Hope that makes more sense.
Touch to activate, touch to de-activate are fine as you are changing a state only, so a finger covering when touched works well
When adjusting time values the touch area for each number to roll them up or down is too small and your finger covers the number you are changing so there is difficulty setting the values correctly.
Hope that makes more sense.
Yes, that makes more sense, thank you for clarifying. We can blame the smartphone era for this widget (and all widgets that resemble it). Another possibility is to add arrows above and below the spinners. If I reduce the height of the units (to be the same as the number rollers) then it should 'just' fit and not look too terrible.
Would this be an improvement? (I'm trying desperately not to modify the response behaviour too much, the widgets are mostly off-the-shelf, so customisation can be reasonably complicated).