PS- If anyone is worried about overwriting the "deselect all nodes" feature of clicking on white space (0.91), the devs have already saved us from that persistent doom by making a double-click required to deselect (or just press the escape key) in 0.92.
Presently, in trunk, single click on white space does nothing. I think selecting, or even toggling the highlighted node is a decent and functional solution to an otherwise unused feature. I'd think most would be glad that it no longer destroys their whole selection to *miss*.
lol -C
On Mon, Jun 13, 2016 at 1:33 PM, C R <cajhne@...400...> wrote:
I also want it to be "toggle" selection, right now it only "adds" to
selection. I don't want Shift to be involved, as the function from a ux perspective then becomes unwieldy, and the whole point of it is to be more nimble/accessible than current method. (Alt+Scroll wheel when mouse is over a node also extends the node selection set without needing to keep Shift down, so this isn't too much of a convention break IMHO).
Keys: I've found Y and F to be "free" so far. However I'd really prefer
"C" which associates to "Closest". C switches to Calligraphy tool, which maybe makes sense in general, however ideally I'd expect tools to be able to "override" the "global" shortcuts for specific features.
For combination keys, yes. For single keys (like 'C'), no. The reason is because you don't want to prevent the user switching from one tool to another, so overwriting 'C' while the Node Tool is selected makes it impossible to switch from the node tool to the Calligraphy tool without first switching to some other tool first.
Why not just highlight the closest node by default on the node tool. Then a single click can work normally (with all associated modifier keys for adding/subtracting nodes from the selection). For users that complain about this innocuous change, we could add a switch or something in the toolbar prefs. I don't know why anyone would complain though. It makes it easier to see what will be selected/deselected when you click.
In short, I don't think this feature needs an alternative mode, or associated hotkey.
-C
I don't know if that is possible though?
-C
On Mon, Jun 13, 2016 at 9:37 AM, Brynn <brynn@...3133...> wrote:
Hi C R, From my simple user's perspective, that seems like it should
help. But the optional distance setting would need to be closer than Inks Prefs dialog (and not require a restart, like grab sensitivity).
Between the brush idea and the key stroke idea, it seems likethey are very similar. Either way, it's the area around the mouse pointer where the node is selected. So it seems like the "brush" select would be more fluid. But how would it be enabled? Do you click to grab the node, or does just touching it with the "brush" select it? This seems very similar to the lasso select which was mentioned earlier in this thread. If the lasso could be made to work with the Node tool (in all systems), then maybe you could just add the "brush" to it? (Of course, keeping in mind my non-technical perspective, hah.)
Thanks for everyone's interest in this :-)All best, brynn ________________________________________________ From: C R Sent: Monday, June 13, 2016 12:54 AM
To: Brynn Cc: LucaDC ; inkscape-devel Subject: Re: [Inkscape-devel] possibly strange question (snap)
See this quick video capture for Blender paint-select feature:
https://www.dropbox.com/s/r38x7q9yjdjggdl/paint_select_blender_demo.mp4?dl=0
As you can, see it's faster and more convenient than anything we've
discussed so far. Precision can be changed on the fly.
Their implementation requires you to commit the selection with the
Escape button, but I don't think this is necessary.
In short, we could do this, but better.
-C
On Mon, Jun 13, 2016 at 12:47 AM, Brynn <brynn@...3133...> wrote:
That sounds helpful too. I would have to try it first, before I know
if it helps with my particular problem.
It sounds like it essentially makes the pointer bigger?
Isn't that similar to what the Grab Sensitivity does? While it
doesn't affect the Node tool, I've tried with the Selection tool. It works great if the objects on the canvas are far enough apart. But on a crowded canvas, it seems to want to select objects next to the one I want to select. I guess Inkscape can't read my mind, and know which object I want.
I wonder if it would be the same case with the node pointer?
All best, brynn
From: C R Sent: Friday, June 10, 2016 1:46 PM To: Brynn Cc: LucaDC ; inkscape-devel
Subject: Re: [Inkscape-devel] possibly strange question (snap)
Blender has a nice solution to the problem of clicking/selecting small
nodes.
If you press "c" it turns the mouse pointer into a circle. You can
adjust the size of this circle with the mouse-wheel, and just paint over the nodes you want to select with it. press escape when done to exit the selection mode. though we could just as easily use the enter key which may be more intuitive.
On Tue, Jun 7, 2016 at 3:48 PM, Brynn <brynn@...3133...> wrote:
Ok, thanks Luca.
Fyi to everyone, Olof is helping make a better and more clear
presentation
of the situation and request. Just take me a little time to learn how
to
make a video (which I should have done years ago).
Thanks again, brynn
From: "LucaDC" <dicappello@...2144...> Sent: Tuesday, June 07, 2016 2:59 AM To: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] possibly strange question (snap)
Brynn wrote
(That would be the first use I've ever found for mouse position values
in
the bottom-right corner, that shows the position of the mouse. If
you're
working in a file where measurement needs to be precise, you can place your mouse on the precise coordinates.)
This could hardly be called a precise positioning as the displayed coordinates are rounded and their definition depends on the zoom level. What you get depends on the discretization of your monitor's pixels
coordinates
translated into document's coordinates. A better way to achieve a precise positioning is using guides: drag
out a
guide, open its dialog to set its coordinates and snap to its origin whatever you want to be exactly there.
Luca
-- View this message in context:
http://inkscape.13.x6.nabble.com/possibly-strange-question-snap-tp4976904p49...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and
protocols
are consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and
protocols are
consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel