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
Usability: export all dtpresets #2383
Comments
This issue did not get any activity in the past 30 days and will be closed in 7 days if no update occurs. Please check if the master branch has fixed it since then. |
Its a feature request not yet implemented |
Feature request not yet implemented or triaged ... |
Would simple "export all user-made presets to given dir" be simplest descirption of this FR? (no exporting of build-in presets) |
yes, exporting built-in presets is not necessary - they don’t get lost when ditching data.db |
Allow export of all user-defined presets Additionally allows import of multiple presets at once Fixes darktable-org#2383
Please check #7405 - does it match your expectations? |
Yep, that’s it |
Allow export of all user-defined presets Additionally allows import of multiple presets at once Fixes #2383
if switching between different test data.db an export function for all presets in one step would be helpful, to simplify reconstruction of a brand new test environment from scratch.
The text was updated successfully, but these errors were encountered: