This was broken last summer when I made the ~/autoplot_data/config/options.properties file be the authoritative control for the properties. I moved my cache from the default position and it seems to be persistent between sessions. Is this the case for you, Ivar?
I think the confusion came when I first migrated prefs from org/virbo/autoplot/ to org/autoplot, and then again from the Java prefs area to the autoplot_data/config area.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also, I'm not sure the fscache location should be stored in the autoplot_data/config preferences, since I'd like for one to be able to move the whole folder from one machine to another when they get a new laptop. Having a reference to a particular directory might break this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here;'s a procedure that shows the bug:
1. move autoplot_data aside.
2. rm -r ~/.java/.userPrefs
3. get old autoplot from Jeremy, for example ~/bin/autoplot.20160728a.jar
4. start this autoplot, reset the cache to /tmp/ap/fscache/
5. start the latest version of autoplot
6. note that the default location is used.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay the problem was the "get" method of the migrate prefs would use the default if the first preferences didn't contain the item. Now the code will check the second to see if it has the preference, then use the default. So this should be fixed in the next release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This was broken last summer when I made the ~/autoplot_data/config/options.properties file be the authoritative control for the properties. I moved my cache from the default position and it seems to be persistent between sessions. Is this the case for you, Ivar?
I think the confusion came when I first migrated prefs from org/virbo/autoplot/ to org/autoplot, and then again from the Java prefs area to the autoplot_data/config area.
I made my fscache location /tmp/jbf/fscache. This is a useful way to see how things are stored on Linux:
Also, I'm not sure the fscache location should be stored in the autoplot_data/config preferences, since I'd like for one to be able to move the whole folder from one machine to another when they get a new laptop. Having a reference to a particular directory might break this.
Here;'s a procedure that shows the bug:
1. move autoplot_data aside.
2. rm -r ~/.java/.userPrefs
3. get old autoplot from Jeremy, for example ~/bin/autoplot.20160728a.jar
4. start this autoplot, reset the cache to /tmp/ap/fscache/
5. start the latest version of autoplot
6. note that the default location is used.
Okay the problem was the "get" method of the migrate prefs would use the default if the first preferences didn't contain the item. Now the code will check the second to see if it has the preference, then use the default. So this should be fixed in the next release.