search

DeBesten / opentx

Automatically exported from code.google.com/p/opentx
0 stars 0 forks source link

Delete Function is not working in Tx #106

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Which board (stock / gruvin9x / sky9x / Taranis) are you using?
Taranis
What is your openTx FW version?
2688
What is your openTx EEPROM version?
215
What steps will reproduce the problem?
1.In Tx go to Custom Functions Tab
2.Press enter key long
3.select delete
4. press enter
5. turn off transmitter
6. turn on transmitter deleted line is back.

What is the expected output? What do you see instead?
Expected to delete function that is playing track -- instead it still plays the 
track.
Please provide any additional information below.

Original issue reported on code.google.com by hhsphoto...@gmail.com on 13 Aug 2013 at 11:29

GoogleCodeExporter commented 8 years ago 
I just had a thought.  This is using my pre-release (suppose to be a release 
version) transmitter.  I have not tested this with my production Taranis yet. 
I'll do that as soon as I get home from work.

Original comment by hhsphoto...@gmail.com on 13 Aug 2013 at 11:32

GoogleCodeExporter commented 8 years ago 
Just checked my production transmitter and it has the same issue.

Original comment by hhsphoto...@gmail.com on 14 Aug 2013 at 1:00

GoogleCodeExporter commented 8 years ago 
Reproduced on my Taranis, 

However I dont really thing this is a defect, but due to the current 
implementation of openTx. To save your changes you need to exit the current 
screen which you are editing items. Correct me if im wrong but I think that all 
changes even though visually shown only get committed to the TX memory once you 
exit the screen.

If this is the case, would be great to introduce a new feature which indicates 
to the user that. 

#1. You are in "Edit Mode" 
#2. There are unsaved changes. 
#3. An alert before powering of mentioning any unsaved changes, or just save 
them without any further user interaction.

Original comment by dehigama on 15 Aug 2013 at 7:40

GoogleCodeExporter commented 8 years ago 
I reported this as issue #88. Bertrand says it is fixed and will be out in the 
next release. (was on 2688 when reported.

Original comment by oldjoecl...@gmail.com on 15 Aug 2013 at 1:23

GoogleCodeExporter commented 8 years ago 
Right! Already fixed. Will be in next release.

@dehigama: no, changes are directly saved, unless you open a new issue because 
of another bug elsewhere ;)

Original comment by bson...@gmail.com on 16 Aug 2013 at 8:39