-
Notifications
You must be signed in to change notification settings - Fork 3
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
panic #155
Comments
actually, duplicating any circle at an order > 0 in this scene will panic |
smaller reproduction s0.txt |
some components are added in post_load, so if a circle doesn't yet have them we don't want it in the process queue... this avoids the panic in #155
why does a loaded (unready) circle end up in the queue only with this setup? edit: process has nothing to do with it. reorder has to target something, doesn't matter what.. |
ah, it's cause rise is constantly opening the wh, so connected to a reorder meant that the reorder is always sending an OrderChange event yup, this also does it so, b51ed80 is the best protection, but i wanna try figuring out a better way to handle rise/fall wh opening as well |
done 576cfba |
this panics when duplicating the top right empty at order 2 (doesn't matter it can be at order 1)
scene file: process.txt
The text was updated successfully, but these errors were encountered: