Jon Denning

that's a great tool idea!

the previous implementation should be "snap to boundary" instead of "slide along boundary". here is a quick explanation of how it worked... at the very start of the tool (before...

i believe this issue is resolved!

will take another look

ok... after digging, the problem is caused by another add-on freeing the bmesh of the edit mesh. commenting out one line in Gamiflow (https://github.com/matheinig/GamiFlow/blob/main/addons/Gamiflow/helpers.py#L96) works around the issue! below are...

note: if the bmesh is invalidated, so are all of the saved bmverts, bmedges, bmfaces. this causes problems for some tools if some data is collected at first and used...

try commit 2d88be6!

hmmm... will look into it. I think I know what's up

ah, silly me. commit 798e913 should fix that!

ok. i've beat against this problem for a while now, but then I discovered something else. it looks like Gamiflow is also creating a bmesh of the edit mesh, doing...