6a33801463
default tab moved to i18n
2014-05-06 16:45:26 +02:00
74e9256e75
correcting MSP implementation, optimizations
2014-04-11 15:11:59 +02:00
36a79f8902
simplify
2014-03-20 22:27:53 +01:00
985d5233a2
resolving callback hell in backup routine
2014-03-20 22:19:27 +01:00
9b29f78e3e
whitespace trimming run
2014-03-08 06:25:15 +01:00
dfdddad767
polishing backup object
2014-03-07 17:43:53 +01:00
0339f87d86
more robust approach
2014-02-22 21:43:17 +01:00
7d4e7f8310
write to file IO bugfix
2014-02-22 21:23:06 +01:00
8686a45831
adding more user-notify messages
2014-02-04 18:52:21 +01:00
b9a09b38a0
callback based upload for restoring settings
2014-01-15 14:31:03 +01:00
10caea40d4
don't allow reading files bigger then 1MB
2014-01-15 13:07:51 +01:00
957e1d3bd4
extending backup support (MISC)
2014-01-15 13:05:19 +01:00
6992f4b7f9
removing obsolete timeout
2013-12-16 11:01:00 +01:00
fd62b8568c
validation
2013-12-12 17:10:10 +01:00
e7a02d0e21
moving to GUI integrated interval/timeout model
2013-12-11 18:57:29 +01:00
29343686c5
upload section for the restore function
2013-06-18 00:14:49 +02:00
9ad8534f0c
initial strikes for backup and restore featureset
...
currently the backup part (file creation and latest data pull appears to
be working just fine)
restore part of the code is already able to pickup and read the file
(without any version verifications (for now, will add some if necessary
/ needs more field testing)
next step is to push the reconstructed values to the respective data
arrays and objects and then uploading this new data to the flight
controller
2013-06-17 23:36:19 +02:00
cTn