-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simply doesn't work for me, bummer #1
Comments
HI! I didn't tested it with Unity 2018.2.15f1 . Also if you have any other unity inspector editing scripts it may not work. |
Same problem here. I went through the code and it seems that any component with already an Editor script are simply skipped. |
put |
@Roritamashi how about using the foldout in a custom inspector? Is that possible? |
@Nesh108 i dind't tested it on a custom inspector but it may be work or not? |
@Roritamashi it would be nice to have the following (it might already work but I couldn't myself):
Is that doable? |
@Nesh108 i think you need to add the new inspector fields on the script, im i have no idea how to do that sorry |
Too bad :( |
send a PM to the creator to talk with him? |
I have other custom editors that target UnityEngine.Object, which conflicts with this one, so only one or the other can work at any one time. Without rewriting both this and the other one in major ways so they work together, was wondering if you can think of any ways to combine both functionality? Only thing I can think of is to rewrite it so both this and the other one handles only the SerializedProperty that it needs to, and let the other one handle other properties. But both this and the other editor are designed to draw the entire object, not just individual properties so it's a lot of work to rewrite them |
was excited to use this, doesn't do anything tho, using as referenced in the readme
I'm using Unity 2018.2.15f1
The text was updated successfully, but these errors were encountered: