Under review

Unable to edit "Custom Property" name field sometimes.

Alan Kent 2 months ago updated by Peter - Soxware Developer 2 months ago 3

This feels like a bug. I created a "Generic" project, I created a dummy object and added the scripts I wanted to animate properties for. I set that is the pose object. It created the root transform/rotate/scale properties. In Configuration/Properties I set "Properties:" to "Nothing". That made transform/rotate/scale go away. I then added a Custom Property constraint.

The problem is sometimes it will not let me change the "Name:" field for the custom property, other times it does.


At first it felt like only every second one would let me change it. Then I wondered if it was it worked if I changed the value before setting "Mode:" to "Component Property" then it worked. Finally I gave up - it just feels random of whether it will let me change the "Name:" field. I just added 5 in a row and none of them let me change it.

After restarting Unity however it started behavior properly again... so reporting in case useful to you, but an easy workaround (restart Unity). May be its a Unity internal bug.


UMotion Version:
1.22p13
Unity Version:
2020.1f2.1
Under review

Hi Alan,

thank you very much for your bug report. I appreciate that.

The problem is sometimes it will not let me change the "Name:" field for the custom property, other times it does.

  1. Is the Name field grayed out in that case? Can you show me a screenshot or a video illustrating the issue?
  2. Can you change other fields of the custom property in case this issue happens?

Thank you very much and I'm sorry for the inconvenience.

Best regards,
Peter

I could change all of the other fields, just not the Name field. I could still highlight the text in the field, just not delete/replace/edit it. I don't recall if greyed out. My memory is not great, but I don't recall the blue line around the field appearing when I could not edit it. 


But it is working perfectly just now, so I cannot confirm. Given that last time it started working after a Unity restart, it could be Unity got itself into a knot. I will try to repeat and reply to this thread with a screenshot. If I get it to repeat again I will add a screenshot to this ticket.

Thanks, yes please update this thread with any information you discover. Unfortunately, with the current information I was not yet able to reproduce this issue on my end (maybe there is some important detail missing yet, like one special type of input action that causes the whole issue).

Best regards,
Peter