Skip to main content
Jun 15, 2016 9:06 PM UTC
Question

Pre-Selection

I understand pre-selecting when you are diving deep into a model.  I've used other tools and the slightest movement of the mouse ends in querying back through the model.  However, it is illogical to have to pre-select something which is already highlighted when nothing is currently selected.  My suggestion is IF nothing is currently selected, when a user RMB's, internally select the geometry and act as if it was pre-selected then internally unselect it if they decide to move to a different entity.  IF there is already something selected than act as it does today.  It's confusing to new users and simply extra work.  Make this new selection paradigm even better please by not forcing a user to pre-select when the system already knows what is being selected shown by the highlight.

3 replies

Jun 16, 2016 12:02 PM UTC

Hi Justin,

thank you very much for your suggestion. I think you raise a good point even though it seems to me at a first glance that there is more to consider.

The RMB on pre-selection does offer pre-selection options (e.g. Pick from list) that eventually determine what exactly you want to select (potentially introducing a refinement resulting in a difference between the pre-selected object and finally selected object).

Examples would be:

- hover over an edge, use RMB pre-selection options to actually select the intent edge

- hover over a surface region in FMX, use RMB pre-selection options to actually select the entire surface

Your suggestion to "internally select the geometry" requires:

1) the system to be able to unambiguously derive the to-be-selected geometry/object from the pre-selection highlighting (which might be possible)

2) the user to already get to the desired (potentially refined) pre-selection (and highlighting) without going to the RMB menu.

The latter point (2) can typically achieved by toggling through various options with quick RMB clicks, but your suggestion would remove a visible icon/command to achieve that from the menus (which would make it harder for new users as well)

So, it comes with a trade off that might require us to actually find another, easy-to-learn way to either:

a) refine pre-selection or

b) post-refine/change a selection (e.g. allowing to change a selection from edge to intentEdge).

I hope, I understood your suggestion correctly and I could clarify the impact.

Anyway, I will take it to and discuss this with the UX team. 

What would be your thoughts on a) vs b)?

Thanks..:Martin

jroegnerAuthor
Jun 16, 2016 1:13 PM UTC

b) would be my choice.  I would counter and say it is harder for new users in the current paradigm as they expect to do something with what the system has already highlighted and instead it gives them nothing leaving them confused (we bring in new college co-ops every semester so this is a continual problem I have to address, the same with casual users).  I want to have the system be smart and make a choice for me if I haven't already made one and then let me change my mind.  It's very similar to the rest of the paradigm PTC has adopted (which is extremely helpful) when creating features the system makes assumptions so the feature can be completed with little knowledge like sketch orientation, depth, direction, dimensions, etc.  The user can change any of it if they want but if they don't they can at least continue. Today you can't continue until you select something.  I know that's a long answer but I hope it helps shed some light on an end-user expectation of why post-refine is a preferred choice.

Jun 16, 2016 1:56 PM UTC

Hi Justin,

this makes sense and actually goes well in line with my thinking for further evolution of our paradigm.

I favor b) as well but it is a bigger project that will not fit into Creo 4.0. We will continue to discuss it though.

Again, thanks for your feedback.


Best regards..Martin