Simultaneously editing and synchronizing files between two devices may lead to accidental data loss. #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Thank you!
In case of such an error, could the current SVG file be copied to the clipboard, enabling users to perform the paste and save operation themselves?
I'm not sure why I didn't think of putting the SVG into the clipboard myself :') It seems like such an obvious choice to make recovering from the error easier...
Anyways, thanks for the report! I was already planning on a change that would fix this issue (and a couple more), I will implement it soon.
This has been partially addressed in v0.3.0.
It's already live on the store, so you can test it out and tell me how it goes.
Personally, I've found that the sync is still flaky when editing on a desktop and mobile simultaneously, and it's easy to get sync conflicts to pop up. Unfortunately, that has more to do with the inner workings of SiYuan's sync system than with this plugin, for this reason I recommend enabling "Generate conflict documentation when syncing conflicts", and closing the editor tab on device 1 when editing on device 2, and vice versa.
It seems to me like sometimes SiYuan doesn't do a Refresh when it's supposed to. Normally, I see that when I edit a document on device 1, and then I sync it on device 1 then 2, the app doesn't reload on device 2. I think it's supposed to, but it doesn't. This causes some issues because, if the app isn't reloaded, the js-draw tab still remembers the old state of the drawing.
Remember that in some cases, conflicts are the intended outcome. If you edit the same file differently on two devices at the same time, then sync, they will generate a conflict, and that's normal.
I know that this system is not ideal, but it's hard to come up with an alternative. I will keep this issue open for anyone that wants to add to the conversation.