The issue with Qt and OneDrive often stems from file access conflicts, where OneDrive’s real-time synchronization or “Files On-Demand” feature interferes with the ability of Qt applications (which may use XML files for configuration or data) to read or write files, potentially leading to errors or application crashes.
File Locking/Sync Conflict: If an application is writing to an XML file while OneDrive tries to sync it, the file can become corrupted or access can be denied.
Workaround: Ensure the application saves the XML file to a location not managed by OneDrive initially, and then move the complete, closed file to the synced folder
Thank you for your efforts. I am aware of the many risks of clouds, but almost a decade ago I downgraded my infrastructure and migrated to cloud. Before I had a NAS, but for one man band with low IT affinity it was just to much work.
As I use different devices in different places I cannot image working without file synchronisation. I will do additional backups of SeamlyMe files in case something goes wrong.
Rule of thumb is have 3 copies… with one copy in a different place. That could be a cloud copy. From my perspective the cloud doesn’t work as 1) You may loose internet at the worst time. 2) When you work in the video & audio industry uploading terabytes of data is impractical.
And that could be precisely the issue here. Something is mucking up the EOL chars of the XML files. Amother user has pointed directly to saving Pattern files to OneDrive as an issue.
I use Syncthing for my file synchronization between computers. As long as I keep at least one computer on as a pseudo-server, & don’t shut off a computer too soon after altering the file content of the Seamly folder it works well enough. It wouldn’t work if I turned all my computers off when I’m not physically using them.
I’d eventually like to have one computer functioning as an actual central server, & proper regular backups, possibly with the rest remote-booting from it, but that’s not on the cards yet.
