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
To achieve this, perhaps another sealed class called TriScriptedImporterEditorFallback can be generated which has the [CustomEditor(typeof(ScriptedImporter), true)] attribute and that attribute can be removed from TriScriptedImporterEditor, allowing it to now be abstract:
Note that this convenient inheritance is already available for TriEditor so for normal Editor implementations, I can simply inherit from TriEditor instead of Editor. I basically want the same convenience for TriScriptedImporterEditor.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently my ScriptedImporterEditor's structure has to be as follows to support Tri-Inspector:
However, I'd like to write it as follows instead:
To achieve this, perhaps another sealed class called
TriScriptedImporterEditorFallbackcan be generated which has the[CustomEditor(typeof(ScriptedImporter), true)]attribute and that attribute can be removed fromTriScriptedImporterEditor, allowing it to now be abstract:Note that this convenient inheritance is already available for TriEditor so for normal Editor implementations, I can simply inherit from TriEditor instead of Editor. I basically want the same convenience for TriScriptedImporterEditor.
Beta Was this translation helpful? Give feedback.
All reactions