Closed raslab closed 3 years ago
Thank you for reporting.
What version of Unity do you use?
Oops, forgot to attach to report, sorry. Unity version 2018.4.0f1
Seems to be similar to #34.
At versions v0.4.0+ you can disable this message at Window/OneLineSettings
by turn off the Culling column.
As I said in https://github.com/slavniyteo/one-line/issues/34#issuecomment-478413485, one of my magic optimizations is broken in the latest versions. But you affected by this only if your consist of very large arrays (optimization allow not to draw invisible elements).
Looks like same but not fully. In #34 problem then in 2019 Unity s_CurrentInspectorWindow
field deleted but in this case we just not using inspector window - we using custom editor window. In this case s_CurrentInspectorWindow
exist but null.
Exception throws at OneLine.InspectorUtil.get_ScrollPosition
, in case of reflection didn't found inspector field - exception was thrown by few lines earlier.
Thanks, turning down of content culling helps :) But it saves to local Prefs (not in Project Settings) and I can't share this solution to all team via git, so just commented exception for next OneLine update.
Sorry, I can't take a screenshot now (because I don't have Unity installed right now), but there is an option to store settings in ScriptableObject.
As said in the description (you can see it in the Inspector when you open Window/OneLineSettings
), you can choose where to store your settings: in ScriptableObject or in EditorPrefs. See https://github.com/slavniyteo/one-line/blob/master/Editor/Scripts/Settings/SettingsEditor.cs#L22.
Don't forget to click the Save button =)
Wow, it's work, thanks)
Closed with #v0.5.2
In case of using some global editor window with small child editors, OneLine flag in child objects can fall.
For example:
Some scriptable object
Some editor window
In this case we catch error because InspectorUtil can't find inspector window (in this case we using custom editor window)