Skip to content
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

Selection problems #28

Open
jonnor opened this issue Nov 29, 2013 · 5 comments
Open

Selection problems #28

jonnor opened this issue Nov 29, 2013 · 5 comments
Labels

Comments

@jonnor
Copy link
Member

jonnor commented Nov 29, 2013

On branch the-graph

  1. It is very tedious to make single-node selections, which is what I want to do most of the time
  2. The icons for node selections are very confusing. I often delete my nodes when I try to get single selection, thinking the Ø means "clear". And the V action is in no way opposite of Ø, and I don't really understand when I would want to use it.

Opinion:

  • Single node selection should be default. Multiple selection is a secondary interaction, and can on the desktop be available by using a modifier+click. Box-select and/or lasso-select are also very useful selection tools.
  • When multiple nodes are selected, operations like move should operate on all of the objects in selection
  • Destructive operations like node deletion must be undoable
@bergie
Copy link
Member

bergie commented Nov 29, 2013

Undo is covered by #23

The tickmark icon for clearing a selection is coming from Android's Action Bars, as is how selecting items in general. So it should behave very similarly as, say, selecting messages in the GMail app.

@bergie
Copy link
Member

bergie commented Dec 1, 2013

To make things clearer, deletion is now using a trashcan icon everywhere

screenshot 2013-12-01 at 05 45 07

@bergie
Copy link
Member

bergie commented Dec 1, 2013

Single node selection should be default

Probably a point where we might want to diverge based on the pointer event type (touch vs. click). There is a separate tracking issue at flowhub/the-graph#53

When multiple nodes are selected, operations like move should operate on all of the objects in selection

Actually, I'd use NoFlo's grouping support for this. If you want to move multiple nodes as a unit, just make them a group (see flowhub/the-graph#43):

Created an issue for this one at flowhub/the-graph#59

@forresto
Copy link
Member

"Make them a group" should be as fast as drawing a selection box, then dragging the box.

Then to make that temporary group stick would be another action. (⌘-G)

drag to select then move

@WilliamRClark
Copy link

How does group selection / creation currently work? Shift click is usually more standard on multiple platforms. Keep in mind the OSX command key isn't going to work on Windows. The equivalent control-G will usually open menus in Chrome and other browsers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants