Fix custom prop logspam #683
Merged
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
…te member after refactoring recording entity class hierarchy.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
First commit fixes some log spam introduced with v22..4.0 . There is no dysfaction, only log flooded with pointless entries.
Second commit fixes fallout from refactoring recordings entity class hierarchy. Member
m_configUuibelongs into base classRecordingBaseonly, but somehow in derived classRecordinganother member with this name and type sneaked in during refactoring, leading to writing values to base class member, but reading from derived class member. This prevented proper updating the property.Plus, some cosmetics along the way.