Thinking on that, there’ve been many cases where this change would be great for clarity, but there’s definitely sometimes where it would just at clutter, so I’m not really sure about how to resolve that…
And while on the topic of reflection… The dropdown list for reflection can get really huge at times, is there any way for it to be coded so that it only shows top-level items, then inherited components (say from a base class, and then from a monobehavior) get put into sub-dropdowns, rather than everything thrown into a huge list. Attached is a screenshot with the issue
i.e., What I mean is the following:
1
2
3
4
5
6
7
EnemyComponent->
->FunctionA
->FunctionB
BaseEnemyComponent->
->BaseEnemy Functions
->MonoBehaviour->
->MonoBehaviour Functions
Thoughts about that, if it’s even possible to do with reflection?
