03-30-2013, 10:58 AM
using ... 22-26
Having separate menu listings is a backwards step (imo) ... it's the equivalent of having all the move (or any other basic command) options listed in the first menu.
The natural place for booleans to reside (in wings core, if it gets there) is in the object / body menu as a single listing - this is how it should be approached - imo.
I've only had a quick play - with subtract, mainly - so comments on that.
As oort (and I previously mentioned) better use of the info line could be made ... I'd suggest going much further than oort
Instead of just
L: Boolean Subtract (as user hovers over this option)
L: Boolean Subtract [Subtracts 2nd object(s) from 1st object(s) - ALL 1st objects MUST be combined before using Boolean Subtract ]
(could use ... and probably better, imo ... 'primary' and 'secondary' instead of 1st / 2nd ...but depends on info line space.
I note that whilst subtract seems to need primary objects combined prior to op ... union doesn't ... also needs sorting, imo.
Next stage
Instead of L: select second bodys for CSG R: Execute
L: Select secondary object(s) to subtract from primary object(s) [secondary objects DO NOT need to be combined] R : Execute
Obviously if subtract worked in the same way as union, then appropriate text could be removed.
Aim should be to provide user with all relevant info (if possible) so's they get what they expect to get - in a clear, consistent manner ... without any surprises.
Personally, I don't see the need for separate (main menu) listings for the 2 other options that've arrived on the scene (inverse / ++)
Think such things as these should be made available to user in the same way as other similar existing tools - eg pressing 1 for dark side of moon option on Tools | Connect.
Not returning hard edges looks / feels better (to me) ... if I was using Booleans ... this is the pref I'd probably use
pp
btw - can't seem to find power user option ... to add final selected element / object to total (with RMB execute) ?
Having separate menu listings is a backwards step (imo) ... it's the equivalent of having all the move (or any other basic command) options listed in the first menu.
The natural place for booleans to reside (in wings core, if it gets there) is in the object / body menu as a single listing - this is how it should be approached - imo.
I've only had a quick play - with subtract, mainly - so comments on that.
As oort (and I previously mentioned) better use of the info line could be made ... I'd suggest going much further than oort
Instead of just
L: Boolean Subtract (as user hovers over this option)
L: Boolean Subtract [Subtracts 2nd object(s) from 1st object(s) - ALL 1st objects MUST be combined before using Boolean Subtract ]
(could use ... and probably better, imo ... 'primary' and 'secondary' instead of 1st / 2nd ...but depends on info line space.
I note that whilst subtract seems to need primary objects combined prior to op ... union doesn't ... also needs sorting, imo.
Next stage
Instead of L: select second bodys for CSG R: Execute
L: Select secondary object(s) to subtract from primary object(s) [secondary objects DO NOT need to be combined] R : Execute
Obviously if subtract worked in the same way as union, then appropriate text could be removed.
Aim should be to provide user with all relevant info (if possible) so's they get what they expect to get - in a clear, consistent manner ... without any surprises.
Personally, I don't see the need for separate (main menu) listings for the 2 other options that've arrived on the scene (inverse / ++)
Think such things as these should be made available to user in the same way as other similar existing tools - eg pressing 1 for dark side of moon option on Tools | Connect.
Not returning hard edges looks / feels better (to me) ... if I was using Booleans ... this is the pref I'd probably use
pp
btw - can't seem to find power user option ... to add final selected element / object to total (with RMB execute) ?