[Feature Request] Please allow saving tag changes locally to file itself, without needing to "export".
Describe the bug When I make changes to the tag of a picture - like adding a new tag to it, or removing any existing tag from it - that change is saved only the in the app, not to the file itself. When I check that file's property in Windows or in any other app, the file still has all the original tags only, and none of the changes I did in OneFolder.
To Reproduce
- Select any image in OneFolder library.
- Press T to open tag editor and add a new tag to the file, or remove any of the existing tags from the file
- Go to that file's folder in Windows Explorer, right click the file, click "properties", and then switch to "Details" tab, and see value for "Tags".
- The values won't show the changes made in OneFolder.
Expected behavior The tag changes I made in OneFolder, should get saved in the file itself.
OneFolder version
1.0.2
Desktop OS
Windows 11 Pro
Additional context
I found the app via comment in allusion repo. That comment did mention that the need of import / export is planned to be removed in future. Hence, making this post here.
Glad to see you here @bagarwa
So this feature was released but it didn't work well enough so we reverted it. I will look into what happened so we can released it again
Came back here after getting a mail for new release. Has there been further development on the issue I reported? Are the tag data still saved locally in the OneFolder app only OR do they directly get saved the images?
sadly this hasn't changed yet, it is still the same as before
I see today's 1.0.20 release says
"Now as soon as a tag is added or removed from a file, it gets written in the file metadata."
But it doesn't seem to be working on my Windows 11 Pro machine. I opened the app after fresh install. Removed some 3 tags from a photo, and deleted those tags from the left sidebar of the app. Then I opened that photo from Windows Explorer. The photo still has those 3 tags. ☹️
I'm on it, it didn't work on my MacOS build either. But in development it works very well, I think is a problem with the build, it doesn't have the latest changes (I kind of struggled to build the app for release so it would make sense)
@bagarwa can you try it now with build v1.0.21? It works on my mac.
To update just close and re-open the app, it should prompt you
Yes, it seems to be working in 1.0.21!! Yayyyy! Thank you so much. I noticed some other issues though. I'll open separate threads for those.
Feel free to open any issue you may have, I will close this for now