In our project we have a scriptable object that has a list of scene references for each scene in the game. We have 130 scenes in total, and with the default code the property drawer caused it to be extremely slow and unusable.

@joaoborks' patch fixes all of our performance issues, on top of making the interface much more usable.

Totally has my vote approving this PR 👍🏿

@JohannesMP Seems like this is what people want. I will merge it if you are OK with it as well.

Hello @JohannesMP !

Will you merge it ? I just figure out that latest versions of Unity 2020.3.30+ on macOS show UI problems on inspector, like this one below:

In my case, I'm using a list of structs/POCO's. Because of this "glitch", I can't attach the scene reference on inspector 😢

Could you help me? I think that this MR could fix this issue, right?

PS: @joaoborks Meanwhile, could you deploy this MR to your [upm] branch? With this, I could use your fork reference directly on manifest.json

@mfdeveloper I've pushed these changes to my fork's upm branch

Hellooo @joaoborks ! Thank you so much for your and update reply

I updated the link to yours [upm] fork branch, but unfortunately the result is the same 😢

Doesn't matter when I put the script that contains SceneReference field, the component panel title (or the "Add Component" in this case) stays on top of it.

Could you help me with that, please?

Are you still on Unity 2020.3.30?

@joaoborks So sorry for my huge delay to reply to you 😅
Thus, I got this problem only on 2020.x.x. I updated to Unity 2021.x and this problem doesn't happen :)

how it is going? I would totally appreciate it if this PR gets merged :)