Closed K4KDR closed 5 years ago
Yep, I have that as a TODO in two functions within minxss_beacon_decoder.py
right now. Planning to implement very soon.
Done! This is now available in commit f4095835de4fb34d410341839aadf26cc45447d1. Check it out!
The decoder continues to work properly with sample data. It appears that after initially entering your Ground Station info, default information is still used for the first upload of telemetry:
========
========
... but on subsequent launches of the application, correct file names and upload info are used:
... users could find this confusing unless specific instructions are provided to EXIT and RESTART the application after entering your Ground Station details.
Good catch... that is definitely a bad user experience. There are surely some signals in Qt that I can use to trigger the update of the filename after the user changes the ground station info.
Yep! The signal is called "finishedEditing" and it triggers when the user either presses enter/return or otherwise selects some other UI element for primary focus (e.g., clicking elsewhere, hitting tab). Commit 999841006081d5281296e3b70f4c42d7b36c755e includes this.
Wow, VERY nice. I deleted input_properties.cfg as if starting from scratch, so default Ground Station info was present. As soon as I entered my call sign (before even entering lat/lon), the upload file name changed:
... and a test packet continued to decode and upload properly:
(... at least I assume it's uploading correctly - would have to verify on the back-end database)
Verified receipt of your newest packets on the back-end database! Glad this is working! Closing the issue.
Whether your team has a use for it or not, most projects include an identifier of some kind (such as Amateur Radio call sign) in the ground station info so that some tracking or credit can be attributed to the volunteer who is submitting telemetry to your database.