#321 closed defect (fixed)
AnimationSequence objects may incorrectly share state
Reported by: | Owned by: | anonymous | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | General | Version: | 0.2 |
Keywords: | animation | Cc: | |
Blocked By: | Blocking: |
Description
Creating two distinct animation sequences then running one concatenates the sequences, where they should stay separate.
Fix is to add a line to the AnimationSequence? constructor:
this._anims = [];
The prototype defines an empty array, but the instances share it except in the case where one calls removeAll. This line gives the instance its own array of animations.
Change History (3)
comment:1 Changed 15 years ago by
Milestone: | → 0.2.2release |
---|---|
Status: | new → assigned |
comment:2 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
(In [2800]) fixes #321