-
Notifications
You must be signed in to change notification settings - Fork 177
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
Box select a set of nodes #53
Comments
That doesn't sound like a bad idea, assuming that we can disambiguate this from the other background gestures like scrub to delete or draw box to add a node |
A threshold should feel better here than it did with panning, since we're not expecting anything to move immediately. Are there systems without mousewheel events? (They could still navigate by dragging the minimap.) |
@forresto you mean systems without a mouse wheel & without a multi-touch screen? Sure there are, but I suppose that isn't a big number in our target audience. And as you mentioned, they can navigate with the minimap. We could possibly even try to detect these two things (touch capability and mouse wheel availability), and lacking those show small arrow buttons near the map. Or maybe just do keybinding to arrow keys? |
This also affects #58 |
As described in noflo/noflo-ui#28, this is a place where we may have to provide different behavior for mouse and touch:
|
to do: meta+drag for selection rectangle |
The selection pseudo-group should capture contextmenu when active. So when you tap-and-hold or right click anywhere in the group you should get the menu for that group. This can include actions like "move to subgraph", "group/ungroup", and even "delete". But those will be implemented in the NoFlo UI |
Since we can pan the graph with two-fingers #34 (mousewheel scroll event and multitouch), dragging on the background should draw a selection box to select multiple nodes.
The text was updated successfully, but these errors were encountered: