Preference miscellaneous, mouse wheel scrolls, does not stick across restarts if changed.
Is there an existing issue for this?
- [x] I checked and did not find my issue in the already reported ones
Describe the bug
Check pref mouse wheel scrolls modules side panel by default. Actions now changed correctly. Quit and relaunch dt, pref has been reverted to unchecked.
Steps to reproduce
check mouse wheel pref quit dt launch dt pref now unchecked
Expected behavior
pref should remain across relaunches
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.1.0+826~g0a226690c1
What OS are you using?
Mac
What is the version of your OS?
15.5
Describe your system
No response
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
apple
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
I can't reproduce this under Windows.
This setting is no different from other settings that you change from the global preferences interface. If the value is changed, it will be written to the preferences file (darktablerc) and read the next time you start the program.
If the next time you start it, you see that the preference value was not saved, this can only mean one thing - it was not written to the file. So, some attributes or file permissions of the darktablerc file are preventing the program from writing to the file. You need to figure out what exactly the problem is and why it is so on your system.
On macOS, unless you specify a different location on the command line when starting the program, the configuration file is .config/darktable/darktablerc.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
Not reproducible, no additional information from the issue author for a long time. So I'm closing this. If comments with additional information appear, the issue can always be reopened.