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
If you have a very large XML, and edit something towards the end of the XML, it will hang up for a substantial amount of time. Even on not so large XML's the time delay after editing a node value is noticeable.
The source of the delay is the CheckChange call in XmlTreeView.OnModelChanged, which appears to be doing an exhaustive search of the XML document on every edit.
The text was updated successfully, but these errors were encountered:
The first condition runs FindNode(node) (super heavy) even when we are not saving, moving that condition to the end I went from duplicating large nodes taking ~11 sec to ~100ms.
Oh, hey nice find, this FindNode call is indeed bogus, and the FindNode implementation was also very bad, expanding everything rather than just the immediate parent chain to the desired node, so I've fixed both of these issues in 2.8.0.18. This will also greatly improve performance of "Find" on large documents.
If you have a very large XML, and edit something towards the end of the XML, it will hang up for a substantial amount of time. Even on not so large XML's the time delay after editing a node value is noticeable.
The source of the delay is the CheckChange call in XmlTreeView.OnModelChanged, which appears to be doing an exhaustive search of the XML document on every edit.
The text was updated successfully, but these errors were encountered: