You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PullTo method (or "Move", as proposed by #91) could implement batches of objects in order to improve stability/performance when dealing with large models.
As discussed with @adecler and @IsakNaslundBh one way of doing it could be to implement PullTo as async. However, this would be in contrast with the rest of the methods, it could be scary to less advanced users, and generally more difficult to debug.
Another way is simply to introduce a mechanism to Pull and Push objects in batches of a certain number.
The text was updated successfully, but these errors were encountered:
A global approach to coping with asynchronous events is going to be required anyway - so good to have that formally on the road map. It has been discussed a few times recently in context of both Adapter Pushing/Pulling as well as loading/creation of formulas in Excel_Toolkit etc. etc. So will be good to start considering users exceptions and required UI for asynchronous events in a flow based programming environment
The
PullTo
method (or "Move", as proposed by #91) could implement batches of objects in order to improve stability/performance when dealing with large models.As discussed with @adecler and @IsakNaslundBh one way of doing it could be to implement
PullTo
asasync
. However, this would be in contrast with the rest of the methods, it could be scary to less advanced users, and generally more difficult to debug.Another way is simply to introduce a mechanism to
Pull
andPush
objects in batches of a certain number.The text was updated successfully, but these errors were encountered: