You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug occurs when creating a scene procedure with a parameter. If the procedure is already in use, it has to be updated, OK. If you try to drag another invocation of the procedure, the drop sometimes generates an AssertionError. The Queen pops up. The drag and drop action is interrupted. I tell students to save and relaunch Alice. Nothing bad seems to happen after.
Here are the steps to reproduce the error:
Launch Alice. Create a new scene.
Add a scene procedure.
Switch back to myFirstMethod and call the new procedure.
Switch back to the new procedure and add a parameter. Tick the box "I understand I need to update the invocations to this procedure."
Switch back to myFirstMethod.
Fix the invocation (or not, it doesn't matter)
Drag a new invocation of the procedure, and drop it above the existing procedure invocation.
This generates an "Assertion Error."
The text was updated successfully, but these errors were encountered:
I followed these steps and the stack generated is a match for Planning bug 464 so I am closing that as dup of this and updating the Jira search where it is one of our more frequently reported issues.
The bug occurs when creating a scene procedure with a parameter. If the procedure is already in use, it has to be updated, OK. If you try to drag another invocation of the procedure, the drop sometimes generates an AssertionError. The Queen pops up. The drag and drop action is interrupted. I tell students to save and relaunch Alice. Nothing bad seems to happen after.
Here are the steps to reproduce the error:
This generates an "Assertion Error."
The text was updated successfully, but these errors were encountered: