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
Currently, sprite scale can be modified in runtime only (go.set("#sprite", "scale", vmath.vector3(...)). It would be very nice if scale could be set in the editor as well.
(forum request: (LINK REMOVED)
2017-08-07 11:42:22 (Mats.Gisselson)
What we really want to do is to move the Scale properties from the components that have it up to the ComponentInstance where the Position and Rotation properties already reside.
Investigate how much work it would be to move the Scale property to the ComponentInstance (engine, bob).
If this is not too much work, it might be worth doing before exposing Scale in the editors.
An alternative approach is to simply expose the Scale property on embedded Sprites and Labels, and hide it on Resources.
Not a lot of work in Editor 2.
Should do this in Editor 1 as well. Difficult?
No change in Bob or the file formats.
Scale property was never hidden for Label resources - Possibly write instructions for how to fix it using the References function in Editor 2 instead of performing a cross-file migration?
If we later decide to move the Scale property to the ComponentInstance, we need to update both editors to perform a simple migration on load. Bob also needs to be patched to read the Scale property from the old place if not present in the ComponentInstance.
The text was updated successfully, but these errors were encountered:
britzl
added
bug
Something is not working as expected
editor
Issues related to the Defold editor
feature request
A suggestion for a new feature
and removed
bug
Something is not working as expected
labels
May 27, 2019
Currently, sprite scale can be modified in runtime only (go.set("#sprite", "scale", vmath.vector3(...)). It would be very nice if scale could be set in the editor as well.
(forum request: (LINK REMOVED)
2017-08-07 11:42:22 (Mats.Gisselson)
What we really want to do is to move the Scale properties from the components that have it up to the ComponentInstance where the Position and Rotation properties already reside.
If this is not too much work, it might be worth doing before exposing Scale in the editors.
An alternative approach is to simply expose the Scale property on embedded Sprites and Labels, and hide it on Resources.
If we later decide to move the Scale property to the ComponentInstance, we need to update both editors to perform a simple migration on load. Bob also needs to be patched to read the Scale property from the old place if not present in the ComponentInstance.
The text was updated successfully, but these errors were encountered: