::sleepily opens one eye::

hmmmmm?... this sounds like someone is dabbling with scary things...

Originally icons for SU where 24x24 and 16x16. However, when the toolbar system got updated for SU8 on Windows they technically changed to 32x32 and 24x24. When I say "technically" it's because the icons shipped in SU wasn't visually larger. They just got updated with extra white-space padding.

The API layer automatically applied padding to smaller icons.

Now, since then my history is a bit fuzzy. I don't recall if out icons now are actually larger. But you could, via the API make a small icon fill out a full 24x24 size. But you should check if the outer edge might overlap with some of the button borders. Verify that they look similar to the rest of the toolbar icons in SU.

Also, I observed recently on OSX that different sizes will might look fuzzy on a low-res monitor. I think the larger icons looks better in the main OSX toolbar, but will look blurred in the floating toolbar.

Not a dumb question. Sometimes it's the little things that make all the difference, though.

@erikcoleman1992 it's a free plugin.

Thanks for the replies!

slbaumgartner, splendid advice. It worked much smoother than I thought it would. The code is attached below. Here are some results from intersecting the two columns in the example file:

Intersect from UI: 983s

Outer shell (*****): 161s

g0.intersect_with g1 (******): 104s

Intersect face pairs: 4s

() Outer shell is probably dominated by the intersect
(*) In order to produce all edges for coplanar cuts two calls to intersect_with has to be made with the groups reversed. The result above is for a single call.

cuttest.zip

CAUL_CutTest0.3.rb

Nice! Great plugin.

You could try the first argument (recurse) of .intersect_with() method set as 'true'.
Also you can include more than one 'entity' in the method's final argument (entities2) - passed as an array of entities...
Say [g1, g2] or even [g1.entities.to_a, g2.entities.to_a].flatten 😕

Bump