Power Inspector | Complete Inspector Rewrite

It's the standard "Prefab" header when inspecting an object in your scene that's an instance of a prefab - not a component i don't think. This is what it looks like in the standard inspector:


I don't have any custom inspectors installed.

Worth noting is that even non-prefab objects have a slightly squished header compared to the standard inspector:




It might be the forward-backward buttons row is cutting into the available height and not adjusting everything else accordingly?

 

May be relevant - i'm now seeing an error in the console that sounds related:

Code (CSharp):

1. System.NullReferenceException: Object reference not set to an instance of an object
2.   at UnityEditor.RangeDrawer.CreatePropertyGUI (UnityEditor.SerializedProperty property) [0x00021] in <f7044ab663d344a2badf1160e57d1c1d>:0
3.   at Sisus.PropertyDrawerDrawer.Setup (System.Object setValue, System.Object attribute, UnityEditor.PropertyDrawer setDrawerInstance, System.Type drawerType, Sisus.LinkedMemberInfo setMemberInfo, Sisus.IParentDrawer setParent, UnityEngine.GUIContent setLabel, System.Boolean setReadOnly) [0x00041] in C:\Users\Nathan\Documents\It-Takes-a-Village\Assets\Sisus\Power Inspector\Code\Editor\Drawers\Property\PropertyDrawerDrawer.cs:235
4.   at Sisus.PropertyDrawerDrawer.SetupInterface (System.Object attribute, System.Object setValue, Sisus.LinkedMemberInfo setMemberInfo, Sisus.IParentDrawer setParent, UnityEngine.GUIContent setLabel, System.Boolean setReadOnly) [0x00061] in C:\Users\Nathan\Documents\It-Takes-a-Village\Assets\Sisus\Power Inspector\Code\Editor\Drawers\Property\PropertyDrawerDrawer.cs:203
5.   at Sisus.DrawerProviderBase.GetForPropertyDrawer (System.Type drawerType, System.Attribute fieldAttribute, System.Object value, Sisus.LinkedMemberInfo memberInfo, Sisus.IParentDrawer parent, UnityEngine.GUIContent label, System.Boolean readOnly) [0x00009] in C:\Users\Nathan\Documents\It-Takes-a-Village\Assets\Sisus\Power Inspector\Code\Editor\Drawers\Provider\DrawerProviderBase.cs:843
6.   at Sisus.DrawerProviderBase.GetForField (System.Object value, System.Type fieldType, Sisus.LinkedMemberInfo memberInfo, Sisus.IParentDrawer parent, UnityEngine.GUIContent label, System.Boolean readOnly, System.Boolean ignoreAttributes) [0x000dd] in C:\Users\Nathan\Documents\It-Takes-a-Village\Assets\Sisus\Power Inspector\Code\Editor\Drawers\Provider\DrawerProviderBase.cs:631
7.   at Sisus.ParentDrawerUtility.BuildMembers (Sisus.IDrawerProvider drawerProvider, Sisus.IParentDrawer parent, System.Collections.Generic.List`1[T] buildList, System.Collections.Generic.List`1[T] results) [0x000a7] in C:\Users\Nathan\Documents\It-Takes-a-Village\Assets\Sisus\Power Inspector\Code\Editor\Drawers\Utility\ParentDrawerUtility.cs:2488
8. UnityEngine.Debug:LogError (object)
9. Sisus.ParentDrawerUtility:BuildMembers (Sisus.IDrawerProvider,Sisus.IParentDrawer,System.Collections.Generic.List`1<Sisus.LinkedMemberInfo>,System.Collections.Generic.List`1<Sisus.IDrawer>) (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/Utility/ParentDrawerUtility.cs:2498)
10. Sisus.ParentDrawerUtility:BuildMembers (Sisus.IDrawerProvider,Sisus.IParentDrawer,System.Collections.Generic.List`1<Sisus.LinkedMemberInfo>,Sisus.IDrawer[]&) (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/Utility/ParentDrawerUtility.cs:2431)
11. Sisus.UnityObjectDrawer`2<Sisus.ComponentDrawer, UnityEngine.Component>:DoBuildMembers () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/UnityObject/UnityObjectDrawer.cs:1928)
12. Sisus.ParentDrawer`1<Sisus.LinkedMemberInfo>:BuildMembers () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/ParentDrawer.cs:461)
13. Sisus.ParentDrawer`1<Sisus.LinkedMemberInfo>:LateSetup () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/ParentDrawer.cs:440)
14. Sisus.UnityObjectDrawer`2<Sisus.ComponentDrawer, UnityEngine.Component>:LateSetup () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/UnityObject/UnityObjectDrawer.cs:1107)
15. Sisus.DrawerProviderBase:GetForComponents (System.Type,UnityEngine.Component[],Sisus.IParentDrawer,Sisus.IInspector) (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/Provider/DrawerProviderBase.cs:395)
16. Sisus.DrawerProviderBase:GetForComponents (Sisus.IInspector,UnityEngine.Component[],Sisus.IParentDrawer) (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/Provider/DrawerProviderBase.cs:376)
17. Sisus.GameObjectDrawer:DoBuildMembers () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/UnityObject/GameObject/GameObjectDrawer.cs:1096)
18. Sisus.ParentDrawer`1<UnityEngine.Component[]>:BuildMembers () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/ParentDrawer.cs:461)
19. Sisus.ParentDrawer`1<UnityEngine.Component[]>:LateSetup () (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/ParentDrawer.cs:440)
20. Sisus.DrawerProviderBase:GetForGameObject (System.Type,Sisus.IInspector,UnityEngine.GameObject,Sisus.IParentDrawer) (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/Provider/DrawerProviderBase.cs:322)
21. Sisus.DrawerProviderBase:GetForGameObject (Sisus.IInspector,UnityEngine.GameObject,Sisus.IParentDrawer) (at Assets/Sisus/Power Inspector/Code/Editor/Drawers/Provider/DrawerProviderBase.cs:235)
22. Sisus.Inspector`2<Sisus.PowerInspectorWindow, Sisus.PowerInspectorToolbar>:RebuildDrawers (UnityEngine.Object[],bool,bool,bool) (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Core/Inspector.cs:1354)
23. Sisus.Inspector`2<Sisus.PowerInspectorWindow, Sisus.PowerInspectorToolbar>:RebuildDrawers (UnityEngine.Object[],bool) (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Core/Inspector.cs:1120)
24. Sisus.Inspector`2<Sisus.PowerInspectorWindow, Sisus.PowerInspectorToolbar>:RebuildDrawers (bool,bool) (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Core/Inspector.cs:1021)
25. Sisus.Inspector`2<Sisus.PowerInspectorWindow, Sisus.PowerInspectorToolbar>:RebuildDrawers (bool) (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Core/Inspector.cs:979)
26. Sisus.Inspector`2<Sisus.PowerInspectorWindow, Sisus.PowerInspectorToolbar>:RebuildDrawersIfTargetsChanged () (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Core/Inspector.cs:973)
27. Sisus.InspectorManager:OnLayout () (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Core/Manager/InspectorManager.cs:928)
28. Sisus.InspectorUtility:BeginInspectorDrawer (Sisus.IInspectorDrawer,Sisus.ISplittableInspectorDrawer) (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Utility/InspectorUtility.cs:295)
29. Sisus.InspectorDrawerWindow`2<Sisus.PowerInspectorWindow, Sisus.PowerInspector>:OnGUI () (at Assets/Sisus/Power Inspector/Code/Editor/EditorWindow/InspectorDrawerWindow.cs:2082)
30. UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

 

I've submitted a fix for the wrong sized GameObject header for review - it was working in 2023.1 and later, but version 2022.2 had slipped through. I adjusted the preprocessor directives to also include versions 2022.2 and later. Thanks for reporting this!

That RangeDrawer.CreatePropertyGUI error indeed looks like it could be the reason for the property drawers being drawn in the wrong place. I'll do some testing with the RangeAttribute in Unity 2022.2 and figure out how to fix it.

 

@nghillaz I think the RangeDrawer error is happening because the RangeAttribute has been added to a field that is not serialized by Unity, and the RangeDrawer relies on using a SerializedProperty internally.

To get around this, I'll add handling to Power Inspector to draw fields using their default drawer if constructing the property drawer based GUI should fail for any reason.

 

Fix for the header size looks good! There's still some odd overlapped text at the top left though:



I believe this is an incompatibility with the Rewired asset, as it doesn't seem to happen for any other objects, and the Rewired inspector drawer doesn't render correctly.

this is what it looks like in the standard inspector:


And in Power Inspector


This isn't a huge deal, as it only impacts one object in my scene, but just letting you know in case it might affect other types of component (and Rewired is basically a core Unity feature, so compatibility with it would be nice)

 

Thanks for the additional details @nghillaz ! I'll investigate and try and figure out what is causing the issues with Rewired.

 

Hello. Just started with Power Inspector and find that my custom editors are not being displayed. I briefly look at the existing forum threads, but no joy. How to get custom editors to show up again? Thanks.

 

Hey @MikeChr !

If you have a custom default editor, you can try setting the Use Editors Over Drawers setting to Always.

 

Hello,why i can not use [FoldoutGroup] Attribute in unity 2019.4.43.

 

Hey @Nelsonlovey ,

Looks like there was an issue in the code for determining what drawer should be used for the FoldoutGroup attribute. There was an assumption in the code that Type.FullName would never return a null result - but turns out it actually can for open generic types!

I'll submit an update to the asset store containing the fix and also send it your way in a PM.

Thanks for letting me know about the issue!

 

is this working in 2023.1.b7 seems like it doesn't wasn't sure.. no errors just inspector view doesn't change at all

 

@Slashbot64 Just tested Power Inspector in 2023.1.b8 and everything looks to be working.

Have you tried if restarting the editor or reinstalling Power Inspector helps?

 

nvm it does work on b8.. deleting library folder helped it

 

Greetings,

I have a few issues with Power Inspector (just bought it).

Is there a way to make the fields name be shown properly in the PowerInspector and not be cutoff?

For example here, we can see that the fields circled in red have parts of their name either cutoff or occluded. The "Shader" label is slightly occluded in the bottom left.
When we compare with the default inspector:

We can see that the labels are shown properly without being cutoff.

Is there a setting I can change for PowerInspector to have that same behavior and see the full labels?

As a follow up question, when I use the tooltips from XML comments, I have this behavior:
We can see the line break on line 2, after the "the". This is because my comment is written for code editors, like so:

Is there a way for me to have it shown without the newline cut? It's okay if there isn't, but it would be cool if there was.

Thank you!

 

Hey @VoltDriver !

You should be able to disable the automatic resizing of prefix labels in preferences using this option or this one. When components have custom editors the automatic resizing feature might not be able to know the optimal width to use.

As for the XML documentation comment parsing, removing line breaks is not an option at the moment, unfortunately.
I do agree it would make sense to remove them unless

<para>

is used, though, so perhaps I will implement this change.

 

Ok, thank you!

 

@SisusCo Hi, I use the FoldComponent.cs you gave me to fold/unfold the components，and there is a bug when use categorized components:
Unity: 2022.1.23f1
Power Inspector: 1.6.8

 

Hey @NaAGames-YangHaoran ,
Thanks for letting me know - I'll investigate.

 

Hey @NaAGames-YangHaoran , the categorized components mode bug should now be fixed in Power Inspector version 1.6.9.

 

Found a few issues if you'd like to take a look.
Hopefully this explains them well enough.

• 

• 

• 

Unity: 2021.3.26f1
PI: 1.6.9
Inspector Gadgets Pro: 7.0

 

Thanks @Bezoro , the pictures are very clear. I'll see what I can do about fixing these.

 

@SisusCo Not sure whether this is known (couldn't see anything in the forum), I'm seeing this when I press play:

Code (CSharp):

1. Unable to find style 'ToolbarSeachCancelButton' in skin 'DarkSkin(Clone)' Layout
2. UnityEngine.GUISkin:GetStyle (string)
3. Sisus.InspectorStyles:.ctor (UnityEngine.GUISkin) (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Preferences/InspectorStyles.cs:112)
4. Sisus.InspectorPreferences:Setup () (at Assets/Sisus/Power Inspector/Code/Editor/Inspector/Preferences/Core/InspectorPreferences.cs:738)
5. Sisus.InspectorDrawerWindow`2<Sisus.PowerInspectorWindow, Sisus.PowerInspector>:EarlySetup () (at Assets/Sisus/Power Inspector/Code/Editor/EditorWindow/InspectorDrawerWindow.cs:1799)
6. Sisus.InspectorDrawerWindow`2<Sisus.PowerInspectorWindow, Sisus.PowerInspector>:OnGUI () (at Assets/Sisus/Power Inspector/Code/Editor/EditorWindow/InspectorDrawerWindow.cs:1818)
7. UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:190)

Unity: 2022.3.9f1
OS: macOS Ventura 13.5.2
Asset: Power Inspector 1.6.9​

 

Ah, I think I might have found this one - looks like I need to set it up here:



Edit: Er, no. that doesn't seem to help

 

Also seeing warnings like this:

Code (CSharp):

1. Assets/Sisus/Power Inspector/Code/Editor/Serialization/JsonConverters/ResolutionConverter.cs(63,4): warning CS0618: 'Resolution.refreshRate' is obsolete: 'Resolution.refreshRate is obsolete. Use refreshRateRatio instead.'

Edit: the other one is aound line 43

Obv, I can add

Code (CSharp):

1. #pragma warning disable 0618

for now but would be good to resolve in the next version.

for the theme buttons, I hacked it to this kind of thing for now (so this isn't urgent or anything):

Code (CSharp):

1. FilterField = skin.GetStyle("toolbarbutton"); // CGM "ToolbarSeachCancelButton")

 

Thanks for letting me know @Colin_MacLeod ! I'll submit a patch to get rid of these warnings. Unity changed "ToolbarSeachCancelButton" to "ToolbarSearchCancelButton" and renamed some other things in the API as well in the later versions.

 

@SisusCo Thanks, but like I say no urgency on this at all my end.

I did notice another thing. At some point Power Inspector seems to give up life on me. I'm using an asset with a lot of custom controls right now, so I switched back to Unity Inspector with the Power Inspector tab hidden - not sure whether that is signifcant.

Either way, when I switch back to Power Inspector, it's blank:



(That's Unity Inspector in Debug mode on the left)

If I restart, it fixes itself, but then after a time, it clears again.

Changing modes to Debug + and so on does nothing. It makes no difference if I click onto another prefab or game object. Only a restart seems to fix it.

As a workaround, would it be possible to add a force refresh to the menu?

 

@Colin_MacLeod Functionality for forcing a complete reload (maybe mapped to shortcut shift+F5) sounds like a good idea!

I'll also investigate how I could improve the reliability of the system. It appears like perhaps something can go wrong during the setup phase under some circumstances.

 

Sounds good - thanks!

 

@SisusCo It looks like the hotkeys for go back one word (Option-left) and forward one word (Option-right) don't work in text fields on macOS in Power Inspector. Same applies to option-up and option-down, which in Unity's inspector are start of line and end of line.
I have some multiline fields of text to set - without the shortcuts it's hard to edit.

 

@Colin_MacLeod I'll check that out as well.

 

Unfortunately, Power Inspector crashes 2023.2.0b13 immediately for me. On first import, it crashed. Every time I try to load that particular project that has it included, it crashes. Let me know if there's any details I can get you.

 

Hey @JeBuSBrian , it seems I was able to reproduce the crash in Unity 2023.2, so I should have everything I need to get it fixed. Thank you for letting me know about it!

 

Power Inspector version 1.7.0 is now out with these updates:

• Missing GUIStyle issue and Obsolete method warnings fixed in Unity 2022.3.
• Crashing issues in Unity 2023.2 Beta were fixed.
  
• Ability to fully refresh Power Inspector via the context menu of by pressing F5 was added.

@Colin_MacLeod Let me know if the refreshing doesn't work for your use case.
I still need to add support for the missing macOS shortcuts in text fields in the future, but I wanted to get these critical fixes out sooner rather than later.

@JeBuSBrian It turns out the crash occurred because of using reflection to examine a method in a Unity assembly that had the suffix "_Injected". My guess is that method implementation is only injected dynamically at runtime using IL weaving, so if it's examined too early it causes a crash.

 

I've been trying it out. So far, I haven't seen the behavior where the power inspector displays nothing but it does seem to crash Unity on the main scene I'm working on (a special scene to bake meshes).

Steps to reproduce:
• Activate regular Unity Inspector
• In the hierarchy, select a mesh baker TextureBaker component that has a custom editor
• Switch from regular inspector to power inspector

→ long delay, then TextureBaker will deselect

I also saw it completely crash the editor on switching from Unity inspector to Power Inspector, but I'm not sure that was the same object selected.

If you are interested in seeing this, we could make a test scene but will need some time as I'm in the middle of a workflow.

 

@SisusCo Selecting some items in Power Inspector doesn't seem to highlight them in the Project tab:

 

@Colin_MacLeod I don't think I own Mesh Baker unfortunately. If you could send me the Editor.log file after the crash has taken place, that might be enough to help me get to the bottom of the issue.

I'll look into the highlighting issue. Probably the mouse click event is getting consumed by some GUI element when it shouldn't be. I appreciate the great reproduction steps btw!

 

@SisusCo Hi, the bug is still exist in version 1.7.0

 

@caka9999 Oh? I'll look into it - thanks for the heads up!

 

PowerInspector is an excellent plugin, but
After adding the PowerInspector plugin to the project, the compilation time will increase from 10 seconds to over 30 seconds, which significantly affects efficiency

Unity 2022.3.20f1
Power Inspector 1.7.0

 

That's just one of its issues. Redraw issues and GUI errors are incessant, rendering it dysfunctional. I hope we'll see a 1.8 version or even a 2.0 rewrite.

 

I am currently working on a 2.0 version, with the main goal being making the asset much more light weight, as well as modular, so that users can only install the modules that they care about.

I'm using UI Toolkit instead of IMGUI for the rewrite, which should help avoid some of the difficult-to-solve issues that have cropped up in the current version, related to layout calculations and control ID conflicts.

 

Please make sure to optimize the compilation time! This is the reason(15s->50s) why I am unable to continue using Power Inspector

 

@lu526284266 Definitely one of my top priorities!