-
Notifications
You must be signed in to change notification settings - Fork 103
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
Scenic only generates one scene per call #230
Comments
Hi, @Kai-X-Org, I could not replicate your error on my end. |
@Eric-Vin @Kai-X-Org I have confirmed that this error exists. Namely, when you try to close out the pygame display it only generates a single simulation and when you try to close it out, it prevents you from doing so. My script:
My command:
Here is a video illustrating the process. Note, the only way to quit the simulation is to have a pygame_error.mov |
@Kai-X-Org following up on the issue, here I was able to reproduce the issue without a simulator. Also note the fix #238 above actually allows us to terminate dynamic scenarios mid-scenario so it's actually a feature and not related to the issue you indicated in this PR: Here is the current behavior: actual.movHere is the expected behavior expected.mov |
Note, I think this may be the intended behavior for the Cocoa implementation that is used in MacOS environments by |
System Details
Detailed Description
When running a scenic file from the command line without setting the --count flag, Scenic only generates one scene. After closing the window popped up by clicking the red x, Scenic terminates rather than generate another scene.
Steps To Reproduce
I simply ran
ego = new Object
in a Scenic file from the command line.Issue Submission Checklist
The text was updated successfully, but these errors were encountered: