Munther Hindi

Yes, it looks like the same issue and it would. I assume _all_ the new properties would be tested for (and there were additional ones besides traverse_module) and fixed as...

Hello Simon, This is Munther Hindi, one of the contributors to the gdml workbench. Both Keith Sloan and I are currently on vacation and will likely be busy for the...

Booleans should be between objects that have a SHAPE. App::Parts really should not be used as the base and tool of boolean operations, even if they some times seem to...

I would check for shape, not GDMLObject (hasattr(obj, 'Shape')). I believe the current code (that I fixed!) takes into account BOTH placements, but I will double check.

Yes, that's the hole point. The user should be able to do booleans with _any_ solid, not just GDML objects. One should think of GDMLobjects as new specialized solids, but...

Under the Part workbench if you try a cut with a Part that has sub parts:  You get the error 09:02:12 Traceback (most recent call last): File "", line...

@KeithSloan We do export non GDML objects and booleans thereof and have been for a very long time. Extrusions, Revolutions, ... etc.

Yes, the export code does handle booleans of GDML and non GDML objects, as long as there is an exporter for that particular solid. At present if there is no...

Yes, we currently do support export of booleans of GDML and (supported) non-GDML solids:  In case it is hard to see, above is a cut between a GDMLBox and...

> I do a bit different cut, when one object included in another:  and i get  But your method works perfectly. Doing a boolean operation between a volume...