Create an Menue instead of pages

DeBesten / opentx

Automatically exported from code.google.com/p/opentx

0 stars 0 forks source link

Create an Menue instead of pages #137

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

A Feature-Request for an Enhancement:

It is very inefficient to srcoll through the 13 Pages of configuration.
Could you better create top-Menues instead of pages?
It would be easier e.g. to modify telemetry to click on top-menue "Telemetry" 
an get the telemetry-page- you needn't go to the 13th page.

Original issue reported on code.google.com by daniel.k...@gmail.com on 8 Sep 2013 at 6:57

GoogleCodeExporter commented 8 years ago

Original comment by bson...@gmail.com on 11 Sep 2013 at 12:57

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

How would you group the pages into a tree? A menu without making a tree would 
mean just as many presses.
BTW to get to the telemetry page you only need one LONG press of the PAGE key.

Original comment by bernet.a...@gmail.com on 11 Sep 2013 at 2:21

GoogleCodeExporter commented 8 years ago

Closing the issue as there have been no new arguments. Feel free to reopen if 
you have good suggestions.

Original comment by bernet.a...@gmail.com on 23 Sep 2013 at 2:38

Changed state: Invalid

GoogleCodeExporter commented 8 years ago

Sorry for my delayed answer:
I think Graupner does a good job ordering the menues. The Heli-Setup should be 
switchable, if a plane is selcted.
curves and heli-setup could be bundeled- in this case the mixing of functions 
and curves would be easier to understand.
Maybe you could make a poll for ordering the menue.

The templates should be switchable on the first site, and because of this the 
further menues should be reached. Heli, Plane, maybe Delta or v-Tail.

Original comment by daniel.k...@gmail.com on 30 Sep 2013 at 6:12

GoogleCodeExporter commented 8 years ago

Actually there is no plane/heli/glider selection in opentx
So that means:
implement a simplified setup menu
implement menu grouping...

Have you an idea of the time needed to implement such a feature and to port the 
new schema also in companion ?
Probably some full week of work...
Also about heli...
which heli ? 
flybarless do not need cyclic setup, flybar ones need it, so we start, at 
least, with 4 kinds of models.
Such a feature for me is almost a complete rework of opentx.
Maybe if people really need it should ask frsky to sponsor the work...

Original comment by romolo.m...@gmail.com on 30 Sep 2013 at 6:54

GoogleCodeExporter commented 8 years ago

Right. I am ok to work on a different menu ordering, but only if we are paid 
for that. The way it is currently done is perfect for us :)

Original comment by bson...@gmail.com on 30 Sep 2013 at 8:00