search

christopherpow / nesicide

Integrated Development Environment for the 8-bit Nintendo Entertainment System
314 stars 38 forks source link

Linux AppImage build of NESICIDE: should-be-persistent settings do not persist #69

Open robotjunkyard opened 3 years ago

robotjunkyard commented 3 years ago

For example, in NESICIDE->Environment Settings->Code Editor, there are options to change the colors of the "Paper" and also that of the default font. However, changing these and then clicking OK does not change any actual colors, and it's back to what they were when I re-enter that options window. Another example is that Recent Projects does not ever have anything across restarts of the program.

Workaround: I simply rsync or copy /tmp/(location which the appimage extracts all of nesicide's tree)/ to another directory somewhere else (somewhere permanent), and running nesicide from that directory instead seems to persist settings now.

christopherpow commented 3 years ago

Thanks for the report. It's likely a side effect of the AppImage as your work-around demonstrates. I don't have much experience with Linux packaging so the AppImage option seemed perfect -- but perhaps not.

robotjunkyard commented 3 years ago

Nothing wrong with AppImages, in fact as a Slackware user I think they're great, because otherwise I'd probably have to spend an afternoon to manually compile an external dependency or two :smile:.

Where NESICIDE saves its configuration file is a bit unorthodox. I recommend it save configuration settings and other cross-session persistables to $HOME/.config/nesicide/

christopherpow commented 3 years ago

You can have the AppImage create the persistent storage spaces it needs automatically. See this answer: https://askubuntu.com/a/1225307. Note you only need to invoke the AppImage this way once. I've not tried it yet but let me know if it achieves the goal.