UIBlock editor

[Kevdome3000]

For some reason the UIBlock editor doesn't render in the inspector anymore

[adgray1]

Are there any errors in the console?

Unity manages when to show specific editors in the Inspector - it's not something Nova has control over. If there aren't errors in the console, then likely something got corrupted within Unity's internal cache.

Either way, a few things to try (and worth trying in this order):

1. Restarting Unity
2. Deleting the content of you Library folder (the Library folder will be under the same parent folder as Assets and make sure Unity is closed while you do this)
3. Remove Nova from you project, delete the content of your Library folder (same steps as (2)), reopen Unity in "safe mode" if it prompts you with that option (otherwise just let Unity open as normal), and add Nova back to your project through the package manager

[Kevdome3000]

I did not. I just reimported the asset from package manager.

[adgray1]

Without clearing the Library folder, the relevant corrupted bits will remain in the cache.

It's possible by removing the [CustomEditor] attribute, that got Unity to start reading a non-corrupted part of the cache, but if the attribute or BlockEditor class being abstract was the underlying root cause then the UIBlock editor would just never have been visible in the first place - it wouldn't disappear all of a sudden like it did here.

Thanks for following up with the additional info. Will be helpful for future reference if someone else runs into a similar issue!

[Kevdome3000]

I'll give it a try and report back

[Kevdome3000]

Hey, following up on this. I took the steps you suggested, including redownloading the Nova asset in the package manager, and the editor for UIBlock was visible in the inspector again. Then I applied the formatting to all the .cs files in my project(indents, spacing, usings, etc), which I always do, and now the UIBlock editor is not visible in inspector again. So again, I removed the CustomEditor attribute and the UIBlock inspector is now visible again. Could the formatting really be the culprit?

[adgray1]

Thanks for following up!

We don't know exactly what Unity caches, so we can only speculate, but here's a quasi-educated guess as to what's going on (tl;dr Unity is finicky):

Unity might store something along the lines of a mapping between ComponentType->CustomEditorType in its cache. When you apply your formatting changes and then go back to Unity, Unity will do a domain reload. At the end of the domain reload, because you modified the scripts containing the UIBlockEditor type (even if it's just whitespace), Unity may reprocess the [CustomEditor] attributes defined in modified files and remap ComponentType->CustomEditorType. For some unknown reason* Unity may be inserting the mapping UIBlock->BlockEditor into its cache, effectively "corrupting" it. Removing the attribute from that script could be effectively invalidating the "corrupted" mapping, so then Unity loads the right thing.

100% speculation based on the data on hand 😄.

*It would be really odd if the specific formatting changes were the reason, but we have modified that file many times before (both in the process of writing it and just now with a few simple tests) and have yet to run into the issue.

Regardless of what's leading to that "corruption", if the repro to both break and fix is consistent, it might be worth removing that attribute in BlockEditor.cs on our end if for no reason other than it seems like Unity has a bug here, and removing it may help Nova avoid hitting that bug the future.

[adgray1]

We just published Nova v2.1.1 with the [CustomEditor] attribute removed from BlockEditor.cs in. Hopefully this will prevent the issue from reappearing!