Closed philipstarkey closed 4 years ago
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Merged in bugfix (pull request #45)
Fix issue #69.
→ \<\<cset e5fc09947552a549ecb0d964d86c9b923687f3e9>>
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Fix issue #69.
Runmanager was not updating the default shot output folder upon a change in the labscript file (including restoring the labscript file at startup), leading it to sometimes think that the user had intentionally chosen to not use the default shot output folder, even though they had made no such choice.
Other issues may remain, but this resolves one of them.
→ \<\<cset a901ff9795d615e49a7aa0c7ac2f1a2e3dd3d0a9>>
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Merged in bugfix (pull request #45)
Fix issue #69.
→ \<\<cset e5fc09947552a549ecb0d964d86c9b923687f3e9>>
Original report (archived issue) by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Runmanager sometimes fails to update the output folder when you compile a new sequence. Seems to happen pretty frequently when compiling shots very rapidly.