Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"sws: save over current snapshot" only lets you save once, then no more saves until changing snapshot #294

Closed
Jeff0S opened this issue Jul 8, 2014 · 2 comments

Comments

@Jeff0S
Copy link
Member

@Jeff0S Jeff0S commented Jul 8, 2014

From claes...@gmail.com on May 16, 2011 23:04:25

If you are in a snapshot , and create a new track and "save over current snapshot", then change to another snapshot, and then change back, your new track is visible as it should.

If you create a track, save over current snapshot, then create a new track and save over current snapshot again only the first track(first save) will be remembered when coming back from another snapshot.

So you can only make one "save over current snapshot" per snapshot "visit" so to speak. I attached a little video to show the problem.

SWS version 2.0.0 Build 21

Reaper 4.0beta5

OSX 10.6.7

Best Regards

Claes

Attachment: save over current problem.mov

Original issue: http://code.google.com/p/sws-extension/issues/detail?id=294

@Jeff0S
Copy link
Member Author

@Jeff0S Jeff0S commented Jul 8, 2014

From swstim on May 16, 2011 14:09:06

Claes,

Looks like "Save over current snapshot" unsets the current snapshot. (See how nothing is highlighted in the snapshots list?) Then, there's no current snapshot to save over anymore. This should be an easy fix.

Status: Accepted
Owner: swstim

@Jeff0S
Copy link
Member Author

@Jeff0S Jeff0S commented Jul 8, 2014

From swstim on May 16, 2011 23:27:44

Fixed in v.2.0.0 #22 r478 .

Status: Fixed

@Jeff0S Jeff0S closed this Jul 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant