Pick Shortest path interferes with Ring select - Regression #94465

System Information
Windows 10
Nvidia GTX 1070

Blender Version
Broken: Blender 3.0, 2.93LTS
Worked: Blender 2.92.0

Short description of error
In Blender 3.0 shortest path selection interferes with ring selection on my custom keymap where both operators share the same button layout, the difference being a single and double mouse click respectively. When selecting two edge rings, shortest path interferes and adds additional edges to connect the two edges from which a ring selection is produced. Instead, I expect it to only perform two ring selections.

Exact steps for others to reproduce the error

Map "mesh.shortest_path_pick" to Shift + LMB click
Map "mesh.edgering_select" to Shift + LMB double click
Create a cube or monkey
Perform two edge ring selections that do not touch each other, preferably one or two edges apart from each other.
Notice the additional edges selected in between the edges used to pick the ring selection with.

Bugreport - Shortest path & edgering selection.mp4
I also confirmed this on a factory reset 3.0.

Added subscriber: @Hologram

Added subscriber: @PratikPB2123

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @Garek

I can reproduce it on 2.92 and even on 2.80 so I assume it's "working" on 2.92 because of something else. Can you try use File -> Defaults -> Load Factory Settings? Perhaps it's one of the addons (that will give idea of workaround, not to blame add-ons).

@Garek
For me this keymap has worked from 2.83-2.92. Now that I reconfigured my keymap for 3.0, the issue shows. It never happened before.

Here's 2.91, factory reset:
Edge Ring select 2.91.mp4

You can see, it works as I explained, no additional edges are selected in between the selected edgerings.

This is 3.0 factory reset:
2022-01-17 15-54-22.mp4

I have edited my custom keymap in Notepad++, switching around the entries for "mesh.shortest_path_pick" and "mesh.shortest_path_pick" also does not solve the issue, which is how it ended up in my 2.92 install (I didn't remove the default items, only disabled them and added new ones).
So there is nothing I can think of right now that is different between version 2.83/ 2.91/ 2.92 on the one hand and 3.0 on the other, apart from Blender's code base.

Some mouses have separate button for doubleclick, do you perhaps use it? That is only things that comes to mind why you can make expected behavior on older versions while I can't.

Yeah, I have a mouse button mapped to LMB double click.

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Pick Shortest path interferes with Ring select - Regression #94465