MinMaxRange property drawer randomly resets the input occasionally

Environment

• Code source: GitHub
• Code version: 1.19.0
• Platform version: Unity 2014.3.14f1
• 3rd party dependencies:

Steps to reproduce

• Add Empty GameObject to scene
• Create simple script implementing the MinMaxRange property drawer:

using Malimbe.PropertySerializationAttribute;
using UnityEngine;
using Zinnia.Data.Attribute;
using Zinnia.Data.Type;

public class MinMaxRange : MonoBehaviour
{
    [Serialized]
    [field: MinMaxRange(-1f, 1f)]
    public FloatRange Range { get; set; } = new FloatRange(-0.5f, 0.5f);
}

• Add script to Empty GameObject

• Make Empty GameObject a prefab

• Default settings should be: -0.5 ~~ 0.5

• Run the scene then stop the scene

• Change min range to -0.2 (don’t just change the 5 to a 2 delete the whole field and type -0.2

  • Prefab field should now go bold as this is a value change on the original prefab

• Run the scene then stop the scene

• Min range value should still be -0.2

• Change min range to -0.5 (don’t just change the 2 to a 5 delete the whole field and type -0.5

• Run the scene then stop the scene

• Min range has now reverted to 0

Expected behavior

Value to stay at -0.5

Current behavior

Value resets to ‘0’

[thestonefox]

Oh also if you just edit the Prefab (not instance) then it just works like the Script Attached To GameObject anyway and still saves fine

[thestonefox]

Yeah, you can’t set custom datatypes with the SerializedProperty stuff, only what they offer. So that Supyrb SetValue goes through the FieldInfo/PropertyInfo and sets the value.

So something in there is not doing the thing unity expects