-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use and edit 16 bit numbers in MUI menu system. #2529
Comments
I think a 16 bit var doesn't make much sense. How shell the user enter 10000? The user needs to click 10000 times to reach that value. I think it is better to break down the number into 5 variables, each from 0 to 9 (first var from 0 to 5). Then you can calculate the 16 bit value with a10000+b1000+c100d*10+e (a..e are the five variables). There is a similar example here: The above example also updates the next higher value based on the overflow of the lower number however this is not really required. |
agree, it is not practical to edit numbers larger than 100. however we used to edit this type of variables with cursor select system thousandth, hundredth, tenth, oneth one by one and user can select the digit and edit by up-down buttons. also there is another old method called as typematic. a single click adds or subtracts one but if user keeps pressing the button variable starts to increment tenth every second, after several sec. it starts to increment by hundreds every sec etc. |
true, but this could be simply implemented by yourself: Just create a new muif, which displays your 16 bit variable:
Register this muif in the muif table (for example with Then, if the form with this number is visible (by checking the FDS form id with https://github.com/olikraus/u8g2/wiki/muiref#getcurrentformid) , just apply your up / down updates and do a redraw of the menu. |
Thanks, i will use this method. |
is it possible to use and edit 16 bit numbers in mui menu system ?
The text was updated successfully, but these errors were encountered: