This is a route I used to create an on-screen keypad. Looking to understand if anyone else has done something like this and any more streamlined routes:
Created three input fields, one each for hundreds, tens, and ones.
Placed the ten digit buttons on the screen as a keypad.
Gave each digit button three click actions - first moves any digit currently in tens position to hundreds position, second moves any digit in ones position to tens position, third places the keypad digit into the ones position.
Placed one ‘enter’ button with click actions to write the values of the three inputs to three collection properties.
Added a click action to that enter button to multiply the first field by 100, and the second by 10, then add the resulting hundreds, tens, and ones values.
There is also a reset button on the keypad with click action to clear all three input fields in case of error in entry.
@Victor, from your YouTube Aug 12 2020 NumPad Experiment, interested to learn approach you used!
My approach was different. I didn’t use input fields. I rather have one numeric variable, where I store the value. This variable is in a specific Session collection - sessions created every time so that even logged-off users could use pinpad.
For the buttons I have the following action (for “1” +0.01, for “2” +0.02, for “3” +0.03, etc.):
I haven’t tried that, but thanks for a good idea!
The problem with date is that it is stored as number of days since 1/1/1970 (as I remember). And we have standard years, leap years; also number of days in a month vary… so such task is not very easy - how to convert all this to Adalo date
We’ll see, may be I make some research and come with a result
