[Bf-funboard] New Keymap: selection

[Luke Swanson]

Hi, had some trouble sending this, so my apologies if this suddenly shows up as a double-post:

------------------------------

> On Mon, May 14, 2012 at 7:08 PM, Nathan Vegdahl <cessen at cessen.com> wrote:
>> I'm a die hard fan of it
>> going on double click. (It should, by the way :P)
>
> Ah!  Of course, double-click.
>
> How about this:
> LMB click = select
> LMB drag = border select
> LMB drag + Alt = lasso select
> LMB double-click = loop select
> LMB double-click + Alt = ring select
>
> And then shift = add, ctrl = remove.
>
> I think circle/paint select is actually better as a modal tool, since
> that gives the user a clear opportunity to resize the brush.  So we
> can just leave that assigned to C (or some other key).
>
> The only thing this leaves us without is shortest-path select, which
> is important in my experience for UV unwrapping of dense meshes, and
> sometimes for tweaking vertex weights during rigging.  IMO it's not as
> important to be super quickly accessible since it's less frequently
> used (please speak up if disagree), but it shouldn't be too bizarre
> either.  Suggestions?

Hi, just thought I'd put my 2 cents in here, would it make sense to use ctrl-click for this? I see that you have listed ctrl for subtracting from a selection, but unless you're planning on changing something drastically, shift-clicking (or shift-alt-clicking or whatever) on something you've already selected removes it from the selection, which makes a separate modifier key for removing from the selection redundant. So, why not assign ctrl-click to be shortest path select and leave shift-click as add/remove?

>
> Pretty sure mesh edit mode has the most/weirdest selection tools, so
> if we can get this worked out, we can probably re-use for other modes.
>
> --Nathan
>
>
> On Mon, May 14, 2012 at 12:35 PM, Jorge Rodriguez
> <jorge at lunarworkshop.com> wrote:
>> Between shift, ctrl, alt, and double click, you have a lot of combinations.
>> Some of them are crazy hand cramping but if you add up the permutations you
>> get 16 different command inputs. That's not enough to exhaustively put any
>> possible command on a combination, but it should be enough to cover a
>> majority of use cases. That's okay though. You don't need to be exhaustive
>> and cover every single use case. Many of them can be found by combining
>> simpler ones. If we go by the 7 plus or minus
>> 2<http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two>rule,
>> people are unlikely to learn more than 9 combinations anyway.

Er, if memory serves (no pun intended), I am pretty sure the seven plus or minus two rule applies to short-term memory, not long-term memory. In the case of learning keyboard shortcuts you would be using long-term memory.
_______________________________________________
>> Bf-funboard mailing list
>> Bf-funboard at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-funboard
>
>
>_______________________________________________
>Bf-funboard mailing list
>Bf-funboard at blender.org
>http://lists.blender.org/mailman/listinfo/bf-funboard