- User Since
- Jan 30 2005, 5:47 PM (723 w, 1 d)
+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.
@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 this case double click is used, closing.
Sat, Dec 8
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).
Fri, Dec 7
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.
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.
Thu, Dec 6
In general, am not against this, noting some issues though.
Can't redo, 234c1129715a022b5ff95ed3dcd8e275e3661f8c
Bugs need reproducible steps. likely driver / OS related.