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
I think this is a bind markers to input-specific issues, since markers only associate with specific branches when that option is checked (otherwise markers are global and independent of the currently loaded branch).
I'm actually rather surprised this bug wasn't noticed before. I've noticed related marker change anomalies for a while, but finally spent a few minutes and traced the root cause today.
Repro
Open a game and then TAStudio
Place a marker at frame 10
Add a branch 'A'
Add a branch 'B'
Select a frame before the marker and press Insert (or equivalent hotkey) 10 times to move the marker. Don't press update branch.
5a) Alternatively, alt-click drag to move the marker to frame 20.
5b) Note: the issue only reproduces with insert/deletes, not Ctrl+Insert cloning.
Load branch 'A'
Load branch 'B'. Note how the marker is at frame 20, even though the marker change shouldn't have been saved.
Expected behavior
Any marker changes to a branch only save when Update Branch is pressed (i.e., when the branch itself is saved).
I think this is a bind markers to input-specific issues, since markers only associate with specific branches when that option is checked (otherwise markers are global and independent of the currently loaded branch).
I'm actually rather surprised this bug wasn't noticed before. I've noticed related marker change anomalies for a while, but finally spent a few minutes and traced the root cause today.
Repro
Insert
(or equivalent hotkey) 10 times to move the marker. Don't press update branch.5a) Alternatively, alt-click drag to move the marker to frame 20.
5b) Note: the issue only reproduces with insert/deletes, not
Ctrl+Insert
cloning.Expected behavior
Any marker changes to a branch only save when
Update Branch
is pressed (i.e., when the branch itself is saved).Host env.
The text was updated successfully, but these errors were encountered: