This repository has been archived by the owner on Jul 30, 2020. It is now read-only.
fiGenericPropertyDrawerPropertyEditorManager performance #207
Conversation
This file contains 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
The latodo is for an internal todo tracking I use. It slipped through. I changed other occurrences of GetSceneAt's result using `var` instead of the actual type `Scene` in `fiStoragesManager`.
Added cached `fiUnityObjectReference` to use on `OnInspectorGUI()` in `fiCommonSerializedObjectEditor`.
…ger (avoiding using too much linq). Performance boost of about 50% for larger projects (6s to about 3s on my project)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Performance improvements to
fiGenericPropertyDrawerPropertyEditorManager.Mostly some caching and not using linq. Cut about 3s on my project (from 6s originally).