+1 for faster edge-hash

Scene no longer has 'objects', see: https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Python_API/Scene_and_Object_API

Thanks, committed rBd98282ec5487932d5f9f9a25cbdd60302e2dda87 with changes not to reuse objects with matching names, since name collisions with the users objects is possible.

@Julien Kaspar (JulienKaspar), this was planned for quite a while, could you post to the design task? (should have referenced it T54744)

@Brecht Van Lommel (brecht) as far as I can see dirty applies here: internally ID_RECALC_TRANSFORM / ID_RECALC_GEOMETRY means this data needs to be recalculated, and that the current state isn't ensured to be up to date.

In D4043#91728, @Brecht Van Lommel (brecht) wrote:

In D4043#91678, @Philipp Oeser (lichtwerk) wrote:

I could do a quick check and see how it goes for e.g. checking how many vertices are selected say for 10-15 operators on a fairly highpoly mesh?

It is too slow, as a rule we do not do such expensive checks in poll functions. For example the search operator runs thousands of poll functions, and any toolbar with these operators would run it on every UI redraw.

It's possible to make these fast if information about number of selected elements is stored in the edit mesh data structure, that might be some work to track though.

In this case double click is used, closing.

This is working as intended, only picking a single object sets active, closing.

@ThinkingPolygons (ThinkingPolygons) if you have two or more under the mouse cursor, clicking on them cycles between those objects (or pose bones, edges... etc).

In T58963#573021, @William Reynish (billreynish) wrote:

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.

This should check all edit-mesh objects, not just the active one.

Assign item length to variables

Updated the diff ontop of 2.8 branch, also avoid indenting large blocks of code - causes conflicts and is hard to review.

This isn't a bug, increase the clipping range.

Fixed rBd6d76759f8493ca156c597840f9d41a64e326eba

Committed alternate fix rBa304ed1b014e4e0561b810d7dbaa8768b6713ac0

The operator needs to run in the 3D view.

Missing a blend file and steps to redo the error.

Do you mean loop cut or knife tool?
Can't cause a crash with either.

Even though it looks fine using a hash here, it's worth measuring times for a blend file that do a lot of linking and one that doesn't, since library linking uses a binary search.

Fixed rB7e722afc6202fbcbeddd76bafec76c5c0f6195bf

In general, am not against this, noting some issues though.

Can't redo, 234c1129715a022b5ff95ed3dcd8e275e3661f8c

Bugs need reproducible steps. likely driver / OS related.
Closing.

Fixed rBaeffaf75aba037271e843373a52a8022dceece65