When other users in a project have done many changes, hitting "Reload Latest" or synchronizing can take a lot of time. It seems like most of that time isn't actually spent updating the model, but refreshing the currently open views with the new changes. But if 10 transactions/changes have been committed, I can't see the incremental changes - the program is blocked for user interaction while reloading/syncing. Neither do I need to see them anyway, I just need to see the end result. I just need everything up to date, then the views can refresh only once after all model changes have been implemented. So instead of 10 x (implement transaction + update views), I suggest 10 x (implement change) -> 1 x (update views).
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Submit Idea
