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
{{ message }}
Repository navigation
[BUG] Inspector doesn't redraw on selected class change #88
Component is not being set dirty after change of selected class using SubclassSelector.
I am using TriInspector attributes (like ValidateInputAttribute, InfoBoxAttribute) that are dynamically add useful info in an inspector. However, when used with SubclassSelector (+ SerializeReference), there is no redrawing happen. And when SubclassSelector is removed, everything works fine.
The selected managed-reference value was being applied, but the asynchronous popup did not report the edit through the owning property's GUI change check. This left TriInspector's cached ValidateInput and dynamic InfoBox results unchanged. The fix reports the edit through the owning field on its next GUI pass, allowing those results to update.
Verified directly with Unity 6000.3.9f1 and TriInspector 1.15.1. Linux EditMode tests pass on Unity 2021.3.45f2 (50/50) and 2023.2.22f1 (53/53), including regression cases for type selection, null selection, cancellation, and isolation from the adjacent field. The exact reported Unity 6000.2.6f2 was not run. This issue will close when #113 merges.
Activity
mackysoft commentedon Oct 15, 2026
Fixed by #113.
The selected managed-reference value was being applied, but the asynchronous popup did not report the edit through the owning property's GUI change check. This left TriInspector's cached
ValidateInputand dynamicInfoBoxresults unchanged. The fix reports the edit through the owning field on its next GUI pass, allowing those results to update.Verified directly with Unity 6000.3.9f1 and TriInspector 1.15.1. Linux EditMode tests pass on Unity 2021.3.45f2 (50/50) and 2023.2.22f1 (53/53), including regression cases for type selection, null selection, cancellation, and isolation from the adjacent field. The exact reported Unity 6000.2.6f2 was not run. This issue will close when #113 merges.