Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
3
Found in
3.0.0b4
Issue ID
368106
Regression
No
Locked inspectors aren't remembered between runs of Unity
Locked inspectors aren't remembered between runs of Unity
Because the Inspector is used for practically everything, the ability to lock it is extremely useful. With locked inspectors, it often makes sense to have more than one inspector in a window layout.
However, inspector locks are not remembered by Unity across runs or window layouts. This means that inspectors have to be set up every time a project is opened or the window layout is changed.
The current division between settings that are in inspectors (Render Settings, Input, etc.) and that have their own tabs (Light mapping, PVS calculation, etc.) seems pretty arbitrary, except that settings which are newer to Unity tend to get their own window instead of using the Inspector.
The result of this division is that only some settings can be part of a window layout. Others must be opened and then locked to an inspector every time a project is opened or the layout is changed.
I realize that it is not always possible for an inspector to remember its locked target between projects, as that target may not exist in all projects. When it does, however, it would be very useful if the inspector remembered rather than having to be manually set every time.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Add comment