feature: Only reload specific train file on clone track node #319
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow LoadTrainTrackTreeNodes to be called when cloning the track node in a background thread.
Adds all nodes to the UI at once, instead of each time; improves UI responsiveness/time.
I can't remember the speed increase, but iir, it was like 3-5s to 500-850ms "lag"/render lock.
Changing the track nodes to a Linked List may be better so we can insert new nodes at x.
Anything that forces a WinForms update seems to render lock
I think WinForms updates will be necessary from
x -> end, unless the node data is updated under the hood - But node type will still needed to be updatedx -> endas its displayed in the UI