Page MenuHome

Slower response of Blender due to click event in "left click" keymap.
Closed, InvalidPublic

Description

Blender2.80 release
Windows 10 (But I suppose that problem is the same in all platforms)

When you use Blender2.80 default keymap with LeftMouse the keymap have a lot of hotkeys using "Click" event instead the "Press" Event. This make blender extremely laggy, specially in edit mesh. User can also don't select some elements if he move the mouse fast. The user experience is completely ruined for users.

  • That event is used in a lot of hotkeys, I can see at least 30 with that event. Main hotkeys like select a vertex, context menu,... all that events are slower (a lot of slower).
  • The problem exist in a lot of parts the keymap, not only in 3D view.
  • I only see the problem in the mouse hotkeys, but I cannot be sure that keyboards don't have it.
  • I didn't test other keymaps like right click or industry standard.

I mention @Campbell Barton (campbellbarton) because he was who decide to don't use the click event by this problem and work in the keymap, and @LazyDodo (LazyDodo) because he talk about this in devtalk forum.

Details

Type
Bug

Event Timeline

Many applications that use left click select, select on click not press.

This is a down side of left click select in general, since you may want to border select on drag, and pick the object under the cursor on click.

This is working as intended, since making left click select keymap work on press would require a re-design. See T57918: Tweaks & Fixes for Improved Left Click Select Support (Parent task)

Is it a joke? Seriously.

Let's see... I changed all my keymap to "press" instead of "click" and everything works exactly the same but FAST. Exactly the same event that we had in 2.79. In the case that "oh, my God" I select an object at the same time that I make a select box is a problem a thousand times less than the fact of having a lag of 100-200ms at the time of selecting.

Seriously we have thrown ourselves 10 years using left click with "press" event without any problem and now that we get you to do a keymap with left click by default you destroy all the user modeling experience with this nonsense?

https://www.youtube.com/watch?v=2KpFAI3D6TE

You didn't want to use the event "Click" and "click&drag" by default on the keyboard shortcuts because you admitted that it added an unacceptable lag. And it was the keyboard, a secondary input system, not the mouse. And now thousands of users who use left click can work with that without problem? something that if you work quickly makes you lose 20-30% of the clicks? And it's not considered a bug?

How is it working as intended? Is it intended to malfunction?

I do not know, imagine that when you are programming all the pulsations have 200ms more lag and that if you write fast you lose 1 out of every 3 pulsations.

So mybe you gt the idea of wat yu re defendng.

It's a down-side, I'm not defending it - however you are re-raising a topic that was closed months ago.

Please leave reopening and triaging reports to developers. This is better as a discussion on devtalk, it's not a bug.

Let's see, it's not a down-side, it's a huge mistake.

Seriously, this destroy all the blender2.8 LeftClick user experience, all the fluidity of the program,... to avoid a down-side that is a thousand times less problematic.

I have spent months thinking that Blender2.8 was slow selecting and it was the fault of the new viewport and that it would be fixed in the final bug-fixing. I've been 2-3 months without using blender2.8 and I haven't verified that this was still happening. Now, after a vacation, I have returned to the program and I only need a few objects to see that simply modeling is going badly.

It is not important that this was discussed months ago and a very bad decision was made. If a bad decision was made it should not be the user who must suffer for years until Blender4.5 arrives as happened with many other decisions of UX.

And It's not a joke or exaggeration. I've always been going around the codequest and I've been a very critical person, that's true but I told this seriously, this is the biggest mistake I've seen in 2.80 about UX. get together, talk about it and change it.

Please leave reopening and triaging reports to developers. This is better as a discussion on devtalk, it's not a bug.

How can you not consider a bug to have a default setting that makes you fail 1 out of every 3 vertices you select?

It's worse than having a crash.

You can't expect us to start talking in devtalk, reach a consensus, see how many likes each comment has and then make a decision.

LOL. Clicking on a bunch of vertices one by one at a high speed is dumb imo, I'd use circle select or something else. There are much faster selection methods for this.

As stated before, not a bug.

LOL. Clicking on a bunch of vertices one by one at a high speed is dumb imo, I'd use circle select or something else. There are much faster selection methods for this.
As stated before, not a bug.

It is normal, you are part of the minority that uses a cintiq to model and needs to have all the menus on the right side because moving the hand tires you. The only thing you make clear with that comment is that you don't model habitually and that you are really slow in your work.

That problems happens if a user select one or two vertices. The problem is the speed, not the number of vertex. And use constantly the circle when you can make two mouse clicks...