SolveSpace version: 3.x
Operating system: All supported
Add configuration option "default solid model as: union|assembly|difference|intersection" to be able set preferred default solid model type for new solid model groups.
NOTE: Suggest, it would be better if by default "solid model" type would be
assemblyinstead ofunion, as it prevent immediate boolean operations & it would be easier to tune next created solid before applyunion/difference/intersectionboolean operations with previous solid model groups.
Actually by default "solid model as: " set (hardcoded) to union for all new created groups.
As result, on complex models next created solid model group could cause whole model on union operation with previous solid models groups & its sometime hard to tune "united" solids.
This seems like it'd just annoy people who are used to the current behavior, and not do anything about the underlying performance issues.
This seems like it'd just annoy people who are used to the current behavior
That is why I request to add "option" instead of hardcoding single choice.
By default this "option" of course should be set to union, but user would be able to set other option on they wish.
Fair point.
FTR, Maybe it would be enough just add checkbox configuration option "☑ default solid model as assembly", which by default would be unchecked ☐ to provide union as "default solid model" (as it came from SolveSpace v2.x) for this case.
This seems like it'd just annoy people who are used to the current behavior, and not do anything about the underlying performance issues.
AFAICT the entire "force to triangle mesh" system is a workaround for issues with NURBS booleans ;-)
I agree that I'd be very annoyed if this was a new default but I could see it as an option.
I could see it as an option.
Agree.