When taking snapshot, start frame gets set to current frame - Githubissues

LLNL / blockbuster

Automatically exported from code.google.com/p/blockbuster

1 stars 1 forks source link

When taking snapshot, start frame gets set to current frame #52

Closed wealthychef1 closed 9 years ago

wealthychef1 commented 10 years ago

Scott's expectation is that start frame will be set to 0. I think it should be copied from blockbuster. At any rate, it should not be set to current frame!

Original comment by: wealthychef1

wealthychef1 commented 10 years ago

Group: Completed --> New

Original comment by: wealthychef1

wealthychef1 commented 10 years ago

Priority: 7 --> important

Original comment by: wealthychef1

wealthychef1 commented 10 years ago

Priority: important --> 3-important

Original comment by: wealthychef1

wealthychef1 commented 10 years ago

Type: --> bug

Original comment by: wealthychef1

wealthychef1 commented 10 years ago

status: open --> closed

Original comment by: wealthychef1

wealthychef1 commented 10 years ago

Fixed. At some point, this comment was put in the code: //use the current frame number, not blockbuster's looping start frame -- Scott says this is the right thing to do

LOL oh well

Original comment by: wealthychef1