-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Design - Reconcile behaviour when dragging out of the workspace #28
Comments
Scratch also deletes the block if it was dragged directly from the toolbox to somewhere outside of the workspace. |
/cc @carljbowman Something to consider when doing the spec for the toolbox. |
/cc @NeilFraser |
I vote for deleting the block when dropped on the categories. Can't imagine that different drop behaviours on categories vs flyout was an intentional design decision. A larger issue is Scratch's ability to drag blocks to other sprites. SVG can't do that if the SVG rectangle is the workspace (as is normally the case with Blockly). There are two options I see. One is to copy in-flight blocks out of Blockly and onto some new floating layer. The other is to expand the SVG so that it encompases all of Scratch. The latter seems to be a more solid solution with less chance for misalignments. That's also closer to what Scratch currently uses, where all of Scratch is one Flash element, not a fragile collection of stuff. |
In Blockly right now you can actually drag the workspace around and have blocks end up on top of the flyout but not deleted, thanks to the svg. This is pretty rare because usually when the flyout is permanently open, you can't drag the workspace, but that constraint won't apply for scratch. |
Part of spec in #21 |
Update in/active states for flag and stop
Blockly currently:
Scratch currently:
The text was updated successfully, but these errors were encountered: