hello @daniel, the latest beta release includes an improved hasOverlap() function which returns a bool instead of a list of overlap positions. please give a try… thanks!

Thanks for weighing in! Just to be clear, I'm not necessarily expecting things to stay magically compatible – I only am looking for a way to remove overlaps, but leave any points intact that are on the exterior of that combined shape. I think you understood my meaning already, but my initial image was pretty ambiguous, so this shows my general hope better: So, it sounds like the way the Remove Overlap functionality works, it's not that these points are removed as an extra step, but rather that their removal is a core part of the function? And there's no way to "turn that off"? As a simple temporary solution, I have found that I can at least have a visual of missing points by duplicating the glyph to an "overlap" layer, then turning that layer's visibility on. You could run a pre-overlap code getting points that are going to be removed... and add them back in a post-overlap script Is there some kind of accessible list of points to be removed (that doesn't seem very likely), or would I have to find a way to loop through points, and mathematically determine if they're on a straight path?

super! enjoy batching

Great! I've fixed that file and now it works perfect. Thanks, em.

For now, I haven't found a way to directly insert my toolbarItem into the toolbar as I couldn't get insertItemWithItemIdentifier:()atIndex:() to work in the context of my script/extension, but probably I'm just being daft here. So currently I read all the items in the glyph window toolbar, add my item, and use vanilla's addToolbar method to replace the toolbar. That's looking good so far, all the previously present items are there, glyph tools work, and my item shows up (not as a button yet, that's lined up next). RemoveOverlap in the replaced toolbar crashes right now when clicked (I guess I'm somehow breaking the delegate or something), but I hope to get that sorted, too.

this is a known issue, and will be solved in the next version. It will not take that long to release the next version :) (if you want to be sure this is fixed you can send the glif file, so I can test it) thanks

thanks for the data this should be fixed in the next version