-
-
Notifications
You must be signed in to change notification settings - Fork 821
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
Save Settings / Save view not working #3959
Comments
By design. You save location with the "Use current location as default" (or similar) button in the Location panel. |
This is not a bug! This is a feature... |
|
By design saving view only saves view, i.e. direction of look and field of view.
You've been using very old versions then. This change was introduced in 4aab2cd, which was included in v0.15.2 released in 2017. |
Actually, I see what you mean regarding the landscape. It's indeed not saved by "Save settings". This doesn't look intuitive to me indeed, but well, at least we have an option to save it hidden in another place. Current location does get saved for me in current @gzotti Is there a reason why landscape is not saved on saving all settings? |
Oops... Sorry for mistake @freebrowser1 |
The default landscape is stored, openly visible, in the landscape panel. We had dozens of repeating questions as to why settings are not remembered and we have to explicitly press "save settings". In many other programs of the past decade, you just click any single checkbox, and the program remembers every single sub-setting for the next run. @alex-w has a strict opinion on keeping the "save settings" button, while I much prefer this more modern behaviour and am slowly adding the StelApp::immediateSave(...) calls for power users (who currently have to set a hidden flag to activate this). We already have a few settings which behave like that (not needing a global save), like Colors or the selection of plugins to be loaded. Once all settings are "optionally immediate", there will appear another checkbox in the config dialog, and with this activated, the "save settings" buttons in plugins and Config dialog will become hidden as it is then no longer needed. Still for this mode, settings for default location, default landscape and default skyculture will remain manual decisions, to be set in their respective dialogs, and a per-use-case change of them will not be stored for the next run, while e.g. selection of DSO catalogs/filters or gridlines will be used again in the next run. |
I also have a strict opinion on this, since having the settings saved immediately precludes free experimentation, requiring to either remember what settings you changed in this session and not forget to manually revert them, or backing up the config file before running Stellarium. And in my view, the Save Settings button should be the thing that will actually save all the changes that you did, including location and landscape (which could also be saved individually by the checkbox, although the checkbox looks like a strange choice of widget for this). |
These used to be separate checkboxes already in 2008 IIRC. Yes, strange choice. |
Well, I tested it again. |
And if you deactivate the setting "Take location from landscape" next to "use this landscape as default" it should also not be loaded. Then your landscape is just decoration. |
Expected Behaviour
When clicking on Configuration Window => Save Settings and Save View, the current location (set by Location window) and configuration settings (e.g. horizon, daylight, etc on bottom bar) should be saved.
Actual Behaviour
These settings are not saved.
Steps to reproduce
Settings are still the old unchanged settings and location.
System
Logfile
If possible, attach the logfile
log.txt
from your user data directory. Look into the Guide for its location.log.txt
The text was updated successfully, but these errors were encountered: