Refactor classes to use RimNamedObject and RimCheckableNamedObject framework #605
+60
−136
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.
Multiple classes maintained custom implementations of name fields and checked state with redundant
userDescriptionField()andobjectToggleField()overrides.Changes
Refactored 5 classes to inherit from framework base classes:
RimCheckableNamedObjectRimNamedObjectRimCheckableNamedObjectRimCheckableObjectRimCheckableObjectEach refactoring:
m_name/m_isActivefield declarationsuserDescriptionField()/objectToggleField()overridesisChecked(),name(),setName(),nameField())registerKeywordAlias()only where serialization keywords differ from base classExample
Before:
After:
Backward compatibility maintained via keyword aliases. Base classes use "Name" and "IsChecked" as keywords; aliases map old keywords "Active"/"IsActive" where needed.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.