Closed GoogleCodeExporter closed 8 years ago
I don't understand where you would want that to be put?
Original comment by bernet.a...@gmail.com
on 2 Oct 2013 at 8:17
Possibly in the main page where we see the name on the currently selected
flight mode. Or Ideally a new dedicated page showing the selected mix names
and the flight mode, to make the screen less cluttered.
thanks.
Original comment by dehigama
on 2 Oct 2013 at 9:02
really?
Original comment by bson...@gmail.com
on 2 Oct 2013 at 9:03
yes really :) but I guess this feature would require a major overhaul of the
firmware just to help people with over complicated setups to not to select the
wrong mix during flight :) sorry for my ignorance.
Original comment by dehigama
on 2 Oct 2013 at 9:39
I suggest something a little different - ability to store "Notes" with each
model.
Just put a text file with the same name as the model on the card, with some
text you write like what switch and what pot does what.
This can then be selected to show automatically on model load, and then be
accessible directly from everywhere in the menus like the channel monitor.
Easy to implement, and easy to put exactly the description you want to remind
you on the specifics of a model.
Original comment by bernet.a...@gmail.com
on 2 Oct 2013 at 10:35
that is cool bernet, just like a pilots kneebord.
Original comment by dehigama
on 2 Oct 2013 at 1:13
Original comment by bernet.a...@gmail.com
on 6 Oct 2013 at 9:47
While the OpenTx wizards work on this, you can use software like Balabolka to
convert the text with the info you need to speech, save the wav file, and set
a custom function to read the file. I have attached a sample wav file with a
hypothetical checklist.
I think it is cool to be able to have someone read to you, rather than having
to read the screen yourself...
Original comment by ululi1...@gmail.com
on 18 Oct 2013 at 1:10
Attachments:
thats really cool, thanks for sharing! thanks for the gurus who are making this
feature possible.
Original comment by dehigama
on 18 Oct 2013 at 3:33
Will be in next major release
Original comment by bson...@gmail.com
on 7 Nov 2013 at 1:57
Original issue reported on code.google.com by
dehigama
on 1 Oct 2013 at 8:16