As far as I can tell the solution recommended by @Joseph Eagar (joeedh) works in this case. I will test it further but I was able to overcome the hard crashes I have been facing when ediitng the lattice in an operator.

It seems like this bug not just affecting undo delete but also it crashes Blender undoing naming and other Lattice objct related operations

Please make a video shows how you crash it. You can use free "ShareX" for recording video.

Thanks for conforming the bug. Do you know a work around with the API so I can avoid the crash until this is fixed?

Probably settings "auto save " is enabled?

Here is an strace I got under Winx64 10, MSYS

Please record a video of how you are crashing Blender. Your steps are not detailed enough to understand what is going on.

Thanks for the reply. All this sounds good.

I would like to ask the Blenderkit dev if this addon collects data on the users even if the addon is not actively used inside Blender.

I tested this with Python API, and the issue seems to be the result of the center being calculated by averaging the vert locations. Using bounding box of the selected vertices produces much better middle positioning.

I think this modifier bug was affecting other exporters as well.

Thanks Bretch, I will test it and follow up here.

Who knew? Interesting feature at best. I agree with you that this should be off. thanks for the tip

In T61052#610922, @Brecht Van Lommel (brecht) wrote:

It can be reproduced by disabling your network connection. Any code that does network access needs to handle exceptions.

Thanks for the follow up, I am going to test it and follow up here.

I might be able to take the addon maintainer responsibility if the role is mostly reviewing the addons and communicating with the addon developers for inclusion. Just an idea.

I am wondering if someone else also do a basic test with this to see, it crashes their Blender as wel. I cant find why this crashes Blender.

All this sounds really really good, thanks for working on it.

I am wondering if this patch can also deal with drag and drop of external meshes like an obj from the system's file browser? Rigth now one has to go through import to do all that but most 3d applications support drag and drop of mesh from outside.

trace from Linux

Ok I actually went ahead and mapped right button (well it is top and bottom on a pen) of my Wacom tablet to "Ctrl - Left" ,so my right click is actually a lasso selection now. As far as I can tell this is quite a workflow improvement, at least for me and I can definietely recommend this combo to be part of Blender as an option.

I have been a left click (with a wacom tablet) user in Blender for a long time. It worked perfectly for me, especially because I liked the tweaking functionality where I do not need to press a second button to do my model tweaks or animations, just like dragging a node in the node editor.

That is why I added as FR: (Feature request)

@Brecht Van Lommel (brecht) thanks for the pointers.

In D3576#90281, @LazyDodo (LazyDodo) wrote:

Which is one of the reasons i picked sentry unlike other solutions in this space, it's opensource and you can run it on your own servers.

I hope that Blender Foundation eventually does not rely on Sentry.Io or any other 3rd party entity when it comes this functionalty. This is all how it starts, first you want to know about the crashes, then you want to know what was leading to the crash, then how the user interacts with Blender, then you want everyone to have an account with Blender to use it etc etc. Not saying there are such intentions but feature creeps happen all the time. Also I had seen these exact same foot steps with all the apps I used in the past like Maya, Modo, Mudbox, Photoshop etc etc.

I also want to add that this new implemetation breaks the ability to pose the bones with left click (drag and release), which works perfectly with 2.79x or before either with left or right mouse buttons.

@Campbell Barton (campbellbarton) thanks for the speedy fix. Had this bug(or a feature) been recent introduction or been there for quite some time?

I just added repeat steps to the original entry.

I actually just tested this with regular "Save Copy" from the file menu, there is the exact same issue. So this does not seem to be anything about the Python call, might be either a design thing or an issue that was overlooked all this time, I cant be sure.

That is undestandable. I will try testing it once I am able to setup building Blender on my new desktop. I am just hoping that the addition wont make the existing modifier slower when the new bisect feature is not enabled, ideally it should but I just want to make sure.

May I recommend that this feature should be tested on higher resolution meshes against the unmodified mirror modifier to see what the performance penalty is?