I just read on devtalk that the handy double click to loop select is not working anymore. Anyone knows what happened, bug/removed?
I noticed this today and thought it was a bug. Where can I read about it?
Alt click for edge loop select is the main reason I push people to modify their window manager shortcuts before starting to learn blender.
Double click is a better default for sure with or without numpad emulation.
Now that was a really bad move.
SadâŚ
Hope they bring back double-click as a default behaviour.
This was part of the rationale for removing double-click loop select.
However, I believe there was some corner case or something where double-click could potentially interfere, so it was disabled unless the above feature is enabled.
Does anyone know what it interfered with, because it never got in the way of something else in my view?
Anyway, adding it back would be an easy job for the developers. I would support its return due to how quick is makes loop selection. If there is a conflict with something else, then it should be fixed.
This is great news!
Now. When will it work on CentOS?
It depends if the time lost by clicking slowly is outweighed by the gain in time with the faster loop selection.
They could always try to require the two clicks to be closer together as far as time goes. Blender seems to go a little loose on that.
I did a test, there are no issues at all. The click is not even slow. Thereâs really no reason to remove the double click.
I donât get this notion that double clicking is faster than alt+clicking.
Not only can you use both hands at the same time, rather than pressing the same button with the same finger twice in a row - but you can start holding down ALT whilst you move the mouse over to where you need to click - meaning itâs effectively just single clicking on edges.
Also the faster together you make the click requirement, the more unreliable double clicking tends to get, and more prone failing due to any slowdown blender is experiencing. Nevertheless thatâs already adjustable in the user preferences input section under âdouble click speedâ.
Thereâs still the matter of holding the shift
key to select more than one edgeloop.
With only one hand on the keyboard, the selection process is a little easier to do.
Same argument. Holding down modifier keys, especially if making multiple selections in a row, is easier and faster because it means you only need to click once for each edge loop, you can press the modifier keys whilst youâre moving the mouse whereas you canât start the double click until youâve reached your location.
If weâre talking about shift, weâre talking about selecting multiple edge loops, compare double clicking 5 times to holding down a couple keys whilst you click normally 5 times, double clicking is a pain in the ass. And so It even makes sense ergonomically, less clicky clicky, holding down alt and shift is hardly difficult.
Not to mention the propensity for the mouse to move slightly in the middle of a double click if you happen to have a sensitive mouse or a slippery surface, I know my current mouse doesnât suffer this issue significantly, or maybe Iâve taught myself not to do it, but itâs definitely come up in the past.
If you want a technically worse option because itâs what other software does, it has to not conflict or compromise existing features. The devs would seem to agree with that, or atleast Campbell does.
Really funny whatâs happening here.
The double click was not a replacement for the old shortcut, it was an alternative. Why are you even talk about it if you donât even use it and seem to hate it so much? This is a handy feature that only the people coming from other apps will appreciate.
I really donât get it.
Ace_Dragon seemed to think it was a gain in time, a faster method.
I thought Iâd question that, as itâs a notion people seem to share.
As for your other point,
I donât know what you want man. I already told you and showed you, there are no conflictsâŚ
You had to click slowly to activate the selection cycling. This sort of ambiguity in functions and keypresses is what blender traditionally avoids, we shouldnât have to sacrifice that just to follow other software. If it were an option, thatâd be fine (but weâre quickly getting a lot of options that essentially boil down to blender <-> industry), but users shouldnât have to get frustrated with it selecting edges just because you forgot you have to click slowly because some people wanted blender to behave like other software.
Then show me where Iâm wrong. Show me how accidentally clicking too fast doesnât cause a loop select. You canât, because thatâs what a double click is.
If your argument is going to be itâs not slow enough to be an issue, my argument is going to be that it will always be an issue because youâll forget or youâll reflex, and accidentally âdouble clickâ, causing frustration.
There are 2 things one is quality the other thing is quantity.
This was really good feature doubble click loop select.
Make it as an option in startup spash screenâŚ