Skip to content
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

can I flush the data in other's ST without reopen the book #199

Open
yuedingwangji opened this issue Nov 13, 2017 · 1 comment
Open

can I flush the data in other's ST without reopen the book #199

yuedingwangji opened this issue Nov 13, 2017 · 1 comment

Comments

@yuedingwangji
Copy link

When I open one book with my company's computer. as the same time. I open it with my home compter。
when I finsh my editing in my company PC,how can I get the newest data in my home PC,without reopen_evernote_note .
and there is a another question that when I reopen the book, I will have two windows with the editing evernote_note , if I update the note in the old windows because of careless, the old data will cover the new data, how can I avoid this?

@bordaigorl
Copy link
Owner

Hi, thanks for the feedback.
You are making a very good point. At the moment there is no mechanism to handle this, you just have to be careful.

One possible enhancement would be to check if a note is already opened and in that case just switch to the tab. This can be easily implemented.

For the multiple clients scenario, realistically I can only think of offering a "Reload note" command.

To solve the "accidental overwrite" problem robustly, one could implement a check that the version counters match before updating. This will incur in two requests for an update instead of one; however we could also offer a setting for switching the check on or off.

These changes would require some work, if anybody is willing to try implementing them I would be more than happy to review the PR and merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants