PuzzledPaul says ...
"Personally, I can't see why all boolean ops can't be dealt with in the same way...ie user selects one object > Bool op of choice > then selects appropriate subsequent objects ... keep it consistent ."
PP, Let's take the case of UNION. And lets take the case where the user wants to union 5 objects together. Why should user have to single out 1 object from the 5 in order to do the workflow ?
The operations are not mathematically consistent. That is at the root of the problem for me. UNION is commutative operations. Subtraction is not a commutative operation.
I guess ... maybe ... I should just let the user do boolean UNION in two parts (two selections) if they want. If that's essentially what's being argued for. Give me some time to make it more flexible and also more consistent. Points taken.
Maybe it will go like this in the distant future ...
Step 1 ... pick Operation from Boolean menu with menu items UNION, SUBTRACT, INTERSECT, SPLIT, IMPRESSION.
Step 2 ... pick "A" set of objects (SUBTRACT or THINGS to get impressed upon). Or just pick some or all of UNION and intersect.
Step 3 (as optional) ... pick "B" set of objects such as item to be subtracted or more items to UNION or intersect.
Part of the problem I have is the foundational code needs some cleaning up. I might do bunches of under the covers things that don't aftect users for a bit.
"Personally, I can't see why all boolean ops can't be dealt with in the same way...ie user selects one object > Bool op of choice > then selects appropriate subsequent objects ... keep it consistent ."
PP, Let's take the case of UNION. And lets take the case where the user wants to union 5 objects together. Why should user have to single out 1 object from the 5 in order to do the workflow ?
The operations are not mathematically consistent. That is at the root of the problem for me. UNION is commutative operations. Subtraction is not a commutative operation.
I guess ... maybe ... I should just let the user do boolean UNION in two parts (two selections) if they want. If that's essentially what's being argued for. Give me some time to make it more flexible and also more consistent. Points taken.
Maybe it will go like this in the distant future ...
Step 1 ... pick Operation from Boolean menu with menu items UNION, SUBTRACT, INTERSECT, SPLIT, IMPRESSION.
Step 2 ... pick "A" set of objects (SUBTRACT or THINGS to get impressed upon). Or just pick some or all of UNION and intersect.
Step 3 (as optional) ... pick "B" set of objects such as item to be subtracted or more items to UNION or intersect.
Part of the problem I have is the foundational code needs some cleaning up. I might do bunches of under the covers things that don't aftect users for a bit.