max/UnitySerializedReferenceUI
1
0
Fork 0
mirror of https://github.com/maxartz15/UnitySerializedReferenceUI.git synced 2025-11-04 06:45:48 +01:00
Code Issues Packages Projects Releases Wiki Activity

Added not supported types example.

Browse Source 
Classes that has no empty parameters are not supported and not shown(activator can not create instances of them).
This commit is contained in:
Textus
2020-08-13 18:13:53 +03:00
parent 2e08459265
commit 37714bc260
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -6,7 +6,7 @@ Project is provided under Mit license which you can find in inner main folder ("
Known limitations. Known limitations.
- Custom property drawer has no effect. Becouse property is drawn from custom attribute drawer custom property drawer is not applied (unity default behaviour). - Custom property drawer has no effect. Becouse property is drawn from custom attribute drawer custom property drawer is not applied (unity default behaviour).
- Can not serialized types derived from UnityEngine.Object (monbehaviour, scriptableObject) (unity's limitation). - Can not serialized types derived from UnityEngine.Object (monbehaviour, scriptableObject) (unity's limitation).
- Can not create instance of object that does not have empty constructor. - Can not create instance of class that does not have empty constructor(only have private for example).
Known Issues of serialized reference: Known Issues of serialized reference:
- Renaming used type can produce data loss and throws unknown managed type exception. This is unity's bug. - Renaming used type can produce data loss and throws unknown managed type exception. This is unity's bug.