-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
[FR] Refresh Button #163
Comments
Hi @yurijserrano thanks for your idea. We can use the observer method of Obsidian to know if there has been any change. The happy path could be add those changes every x seconds to the database, but like a provisional solution a refresh button its ok for me. The code for that refresh is already implemented, should be easy to add it |
Great idea Rafael Really your idea turns out to be the best workflow, I hope it will be included in a future release
Glad to hear Rafael 😃 Once more, thank you so much for your attention. I wish you a wonderful day. |
good news @yurijserrano , the refresh button could be integrated with #73 . With the new architecture of 2.0.0 I can start to dev dynamic events, so I move the filters to the navbar. You don't need to refresh the view once you change a filter, the data will be refreshed instead. I am sure that fact could cover this request |
I am glad to hear @RafaelGB I am waiting eagerly to see this in the next update. Thank you so much for including. I wish you a great day. |
Good Morning @RafaelGB
I hope you are well and safe
When using your plugin I noticed that when we add new data it is not included in the table and to be included we need to go to a note and then go back to the database.
So, to leave the workflow only in the database I suggest to put a Refresh Button at the top so that the users can update the table without having to leave it.
An example of the button placement can be seen below:
If that is difficult, another alternative is to put a Refresh option in the Database Menu
I am at your disposal for any clarification.
Have a nice day
The text was updated successfully, but these errors were encountered: