-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration doesn't save #5
Comments
I'm not aware of anyone actively working on it. |
I don't believe any work has been done on this in almost a year, and then it was only to pull it out of the main Xastir project and into its own repo. As it barely does more than monitor packets, it's not that useful, and there hasn't been anyone tripping over themselves to add functionality. Something is clearly amiss in the stationsettings.cpp functions that save configuration --- there are saved bits of configuration such as lat/lon and station symbol but they appear to be getting written out as I find that all the interface configuration is correctly saved, though, including passcode and filter. My config file winds up looking like:
|
Oh, yeah. stationconfiguration doesn't even look at the lat/lon setting in the dialog. It never actually gets set. There are no hooks in the UI to update anything if you enter data in the dialog for lat/lon. There's a comment there that makes it look like it just got left out to be figured out later. So it makes sense that nothing gets saved --- the lat/lon part of the station settings is never set anywhere. This is not likely to get changed much unless someone is inspired to start working on Xastir-Qt again. |
I understand this is still preliminary, but the basic configuration (call, SSID, passcode, location) does not seem to save. It does keep the call and configuration for the interface.
Are updates planned, or has this been dropped?
The text was updated successfully, but these errors were encountered: