Closed GoogleCodeExporter closed 9 years ago
Also can`t change servo inverse in limit menue 6/7
Lost cursor control function
Original comment by angoliman@ewetel.net
on 14 Jul 2010 at 10:28
in this version i changed the navigation logic.
Now any cursor navigation is done with the up-down keys
1. a short key-press moves the cursor up-down
2. a long key-press moves the cursor left-right
sorry, i didnt provide any changes information unil now.
Original comment by th...@t-online.de
on 14 Jul 2010 at 3:06
Is there any advantage using this kind of navigation or any limitations which
force to use it?
IMHO it would be the nice to navigate the cursor using the 4button joystick on
the left side of the display and using the two keys on the right side of the
display for "increase" and "decrease" of the value.
Original comment by rudolf.z...@gmail.com
on 14 Jul 2010 at 3:24
Status still VALID
When I change model name or add new model, I can`t reach timer setting !
Original comment by angoliman@ewetel.net
on 14 Jul 2010 at 6:48
I figured that if I switch the radio off and back on then I can go to timer
again. But when I am on THR setting and press DN button again long, then the
cursor goes blank and I am unable to reach timer setting.
Have to circle power to reset cursor.
Wish to have old navigation style back .... :-)
Original comment by angoliman@ewetel.net
on 14 Jul 2010 at 7:06
Ok, have a look at the now working navigation (without issue 33) and then think
about again.
The advantage of the new style is,
1. you can directly move to a matrix position, without moving back to column 0
2. value change is always done with the same buttons (left-right)
a drawback is:
column change needs more patience because of the long-keypress.
But there are not very much columns and you often dont have to change it. And
the last column position is retained for the next visit to the same menu
Original comment by th...@t-online.de
on 14 Jul 2010 at 10:28
Thanks for the comment - but I think I don´t get it.
1. When using the 4-button joystick on the left side it is also possible to
move within matrix-structures with almost no limitations (we have
up-down-left-right - but we can´t move diagonal - not necessary ) - so no move
back to column 0 would be necessary - except there are SW limitations
preventing that.
2. Value change would be with the two buttons right of the display - up
(increase) and down (decrease)
drawback:
You need both hands - but IMHO that kind of navigation would be more intuitive
Original comment by rudolf.z...@gmail.com
on 15 Jul 2010 at 5:27
This is right, navigation would be more intuitive. For this reason I originally
used this concept.
But in this case you need all the cursor buttons for navigation.
For the value editing there are some possibilities.
1. The keys at the right (like you propose). Unfortunately I need this keys for
Exit the menu and for Enter submenus (Menu)
2. In my original impl. I switched the meaning of up-down into edit-value when
you left column-0
3. We could use the menu-key to activate edit-mode, but i dont like modal
interfaces because they are not intuitive at all.
I think its not possible to find an absolutely intuitive navigation without any
drawbacks. I tested several solutions and decided for the least nerving one.
It might be that users have other sensitivities.
If you like, you can checkout the code and play around with other solutions
Original comment by th...@t-online.de
on 15 Jul 2010 at 2:54
Thanks for comment !
Quote:
"Unfortunately I need this keys for Exit the menu and for Enter submenus (Menu)"
Think of the Display as a matrix. Row 0 has 2 columns e.g
EXPO/DR.........3/5
When you enter the menu the cursor is at [3/5].
With up-down-left-right you can navigate in matrix and with the buttons on the
right (I call them now + -) you can change the values.
When done and you want to change the menu use up button of the 4-button
joystick at the left until cursor is again at [3/5].
With left-right you can navigate eg. to [4/5] or [2/5].
You did a great job with the FW and implemented lots of features - the drawback
is that the code is huge in the meantime and that I don´t have the overview
where to change what to get what I want.
On the other hand it´s your FW and you are kind enough to share it with the
world - so you don´t really need to care what people like me say. It´s yours
and if the navigation is what YOU want then go for it.
Original comment by rudolf.z...@gmail.com
on 15 Jul 2010 at 4:22
Original issue reported on code.google.com by
angoliman@ewetel.net
on 14 Jul 2010 at 10:12