You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is linked to this discussion in the SoftRobots Plugin.
When defining a Prefab object, zero(s) will be concatenated to the end if a property of vector type is provided with a shorter vector. @EulalieCoevoet provided a good example:
When running the above code, [1. 1. 0. 0.] will be printed. Although being a good and safe default behavior, this behavior can lead to confusion in some cases. For example, when creating a OglModel with node.addObject('OglModel', src="@mesh", color="0.8 0.7 0.7")
the color property will be appended with a 0.0 to make it 4D, which makes the OglModel transparent, and misleads users to think that the Visual Models are not working properly.
So it could be beneficial to raise a warning when a property value is not provided with the correct dimension.
The text was updated successfully, but these errors were encountered:
This issue is linked to this discussion in the SoftRobots Plugin.
When defining a Prefab object, zero(s) will be concatenated to the end if a property of vector type is provided with a shorter vector. @EulalieCoevoet provided a good example:
When running the above code, [1. 1. 0. 0.] will be printed. Although being a good and safe default behavior, this behavior can lead to confusion in some cases. For example, when creating a OglModel with
node.addObject('OglModel', src="@mesh", color="0.8 0.7 0.7")
the color property will be appended with a 0.0 to make it 4D, which makes the OglModel transparent, and misleads users to think that the Visual Models are not working properly.
So it could be beneficial to raise a warning when a property value is not provided with the correct dimension.
The text was updated successfully, but these errors were encountered: