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
Prevent sprite boxes from being flipped into doit boxes
Or ensure an exception isn't thrown in running update-shape on a sprite box that is a doit box
# Should the "Flip to Doit" command be allowed on sprite & graphics boxes?
Sometimes when trying to click into a sprite or graphics box, I accidentally turn it into a doit box. This also happens sometimes when I hit the wrong keyboard shortcut. When this happens, the change is subtle: the corners of the box change from round to square. The box's label remains unchanged as "Graphics" or "Sprite". I often don't notice until later that the sprite/graphics box has become a doit box.
So I think (1) could improve the user experience.
The text was updated successfully, but these errors were encountered:
This issue raises the question: should the "Flip to Doit" command be allowed on sprite & graphics boxes?
Repro steps
I reproed this on Boxer
3.4.19 2024-06-24
Make > Graphics
menu item)sprite
sprite
to a doit box (Box > Flip to Doit
)sprite.SHAPE
tostamp-circle 20
tell sprite update-shape
Unexpected result: A Common Lisp exception is thrown:
The issue can also be reproed with update-shape repro.box.zip.
Potential fixes
I see two options for fixing the issue:
update-shape
on a sprite box that is a doit box# Should the "Flip to Doit" command be allowed on sprite & graphics boxes?
Sometimes when trying to click into a sprite or graphics box, I accidentally turn it into a doit box. This also happens sometimes when I hit the wrong keyboard shortcut. When this happens, the change is subtle: the corners of the box change from round to square. The box's label remains unchanged as "Graphics" or "Sprite". I often don't notice until later that the sprite/graphics box has become a doit box.
So I think (1) could improve the user experience.
The text was updated successfully, but these errors were encountered: