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
Was trying out the new custom frame count and discovered that UI frame numbers (which can show adjusted frame label numbers) are not consistent with the 'From' and 'To' fields in the Properties pane for tags (which still use the fixed frame count starting at one).
If you implemented the custom UI frame enumeration using an offset value, probably this value simply has not been applied to the values in the Tag Properties pane as well. :3
Thanks for looking into it!
Using ASEprite1.1.10 on Win7SP1.
(Related to #1300)
The text was updated successfully, but these errors were encountered:
I poked around a little and my guess is that this new attribute docPref.timeline.firstFrame() should probably be applied to the from and to values in this line?
Was trying out the new custom frame count and discovered that UI frame numbers (which can show adjusted frame label numbers) are not consistent with the 'From' and 'To' fields in the Properties pane for tags (which still use the fixed frame count starting at one).
If you implemented the custom UI frame enumeration using an offset value, probably this value simply has not been applied to the values in the Tag Properties pane as well. :3
Thanks for looking into it!
Using ASEprite1.1.10 on Win7SP1.
(Related to #1300)
The text was updated successfully, but these errors were encountered: