![\"\"](\"https:\/\/docs.sisus.co\/power-inspector\/wp-content\/uploads\/2019\/04\/using-debug-mode-plus.gif\")
<\/p>\n<\/p>\n
When Debug Mode+ is active, all<\/strong> components and class members<\/a><\/strong> are shown in inspector view<\/a><\/strong>. This includes:<\/p>\n The only thing not revealed is members with the Obsolete attribute<\/a>. This is to avoid exceptions being thrown when they are accessed.<\/p>\n Note:<\/strong> Debug Mode+ also works great when inspecting static class members<\/strong><\/a>.<\/p><\/blockquote>\n This mode can be enabled for a single<\/strong> component using the Debug Mode+<\/strong>\u00a0button Alternatively you can enable Debug Mode+ for the entire inspector view\u00a0by opening the view menu<\/a> from the Power Inspector toolbar<\/a><\/strong> and selecting the item Debug Mode+ > On<\/strong>. Debug Mode+ will be active for everything inside the inspector view, and remains on even if the inspected targets. When you run into unexpected behavior<\/strong>, it can invaluable to be able to select any target<\/a> and see all the<\/strong> data<\/strong> it contains without limitations<\/strong>. Even if a field or a component has been hidden<\/strong> in the Inspector, in the context of debugging, you might want to bypass<\/strong> those restrictions temporarily. Unfortunately, this is often not possible in the default inspector<\/a>.<\/p>\n When you’re testing<\/strong> components that are still works in progress, a common thing you want to do is call some methods<\/strong> on them to observe if everything is working as expected. In the default inspector there is no way to do this, without making changes to code. This process can waste a lot of time<\/strong>, because even minor code changes require the script’s assembly<\/strong> to be reloaded<\/strong>, which costs precious time especially with larger projects.<\/p>\n Additionally, should you forget to remove<\/strong> your temporary test code, such as test buttons you exposed to the inspector, it can lead to unnecessary confusion<\/strong> among users.<\/p>\n Debug Mode+ was introduced to solve all of these problems. Using it you can easily invoke any methods you like with parameters you specify through the inspector. And you can always check the contents of that dictionary field if you would like, even if it’s normally hidden.<\/p>\n","protected":false},"excerpt":{"rendered":" What is Debug Mode+? When Debug Mode+ is active, all components and class members are shown in inspector view. This includes: All non-serialized fields. All fields containing the HideInInspector attribute. All properties. All methods. All hidden components (when Debug Mode+ has been enabled for the whole view using the view menu). Previously unsupported types: dictionaries, ..<\/p>\n\n
Enabling Debug Mode+<\/h1>\n
![\"\"](\"https:\/\/docs.sisus.co\/power-inspector\/wp-content\/uploads\/2019\/04\/DebugModeOnIcon.png\")
<\/strong>found on the header toolbar<\/a>.<\/strong> Debug Mode+ mode will remain active for the component only until the inspected target changes, then it is automatically disabled.<\/p>\n![\"\"](\"https:\/\/docs.sisus.co\/power-inspector\/wp-content\/uploads\/2019\/04\/DebugMode.png\")
<\/p>\n
\nWhen Debug Mode+ is enabled for the entire view, hidden components<\/strong> on inspected GameObjects will also shown in the inspector.<\/p>\n![\"\"](\"https:\/\/docs.sisus.co\/power-inspector\/wp-content\/uploads\/2019\/04\/enabling-debug-mode-plus.png\")
<\/p>\nWhy Debug Mode+?<\/h1>\n