Skip to main content
Apr 5, 2012 5:23 PM UTC
Delivered

Improve selection sequence

Related products:Creo Parametric

At the moment, the selection sequence seems to draw a line under your cursor straight into the screen, and then select the nearest entity to that line first.  This usually means that it selects an edge somewhere on the back of the model, rather than the surface directly under the cursor; and results in me screaming "No, stupid, the thing I'm pointing at!" at the screen.  The surface I actually want is usually about the 17th thing on the list.

Surfaces are the most robust entities to reference, followed by edges, and vertices last; yet the current system seems to pick edges and vertices early, and surfaces at the bottom of the list.

Please can we have a selection sequence which reflects this, and which makes more sense with a shaded view (rather than wireframe, in which perhaps that edge at the back was the thing I was pointing at)?  Perhaps it should first select surfaces which are directly under the cursor, starting with the nearest to the screen; then select all edges within the selection radius, again starting with the 'top', and only then vertices...

{edit}

Alternatively, as suggested in the comments thread, perhaps a selection sequence working strictly on distance into the screen would be more intuitive to use.  This would certainly put the surface directly under the cursor first, which is my usual complaint.

{/edit}

31 replies

Jul 30, 2014 7:38 PM UTC

I think also the selection mode called "Smart" isn't the best for selecting - I prefer to use "Geometry" mode - this works the best for me.

Try to make a mirror or geometry pattern of selected surface and you'll feel my example...

Nov 5, 2014 11:06 AM UTC
Nov 18, 2014 5:02 PM UTC

I agree with Doug.  The mouse-over should only preselect/highlight the top-most entity (surface, edge, or vertex) directly under the pointer, i.e. the first entity along a line starting from the pointer and extending into the screen.  This is more intuitive and how it would work if I were actually holding the model in my hands and pointing to it.  If I want to pick something deeper into the model, I can RMB to query-select or pick from list, both of which should be in order along the aforementioned line .  Then, if needed, I can further refine the selection/list using the filter.

The current method for the order of selection is overly complicated and assumes most everyone works the same way but they don't.  What IS the same for everyone is the way they see their model on screen and understand the design.  Keep the preselection/highlight simple (only the top-most entity according to filter setting) and let the user dig deeper with RMB as needed.  It seems this would eliminate a lot of frustration and performance issues that have been around for years and are well-documented in other posts.

On a related note, highlighting a component in the window should highlight not only the component in the tree but also its parents all the way to the first level in the tree.  Basically, this would be the reverse of current functionality where highlighting the top level subassembly in the tree highlights all its children in the window.  This also was noted years ago but still hasn't changed.

Jun 1, 2015 9:00 PM UTC

I also agree with Doug.  The first item in the selection list should be the very first item under the mouse cursor.  Then you could scroll through the remaining choices with the RMB, or Pick From List options.

Oct 8, 2015 12:49 PM UTC

I am the same opinion. I did nearly same task or idea. unfortunately this topic was opened 2012 and nothing happened till today...

PTC has very good software experts. But the tests for new software should be done by users, which work day for day with it in business.

Jan 22, 2016 4:04 PM UTC

I voted down because the selection process in Creo 4.0 is supposed to change dramatically.

3-Newcomer
Jan 22, 2016 4:24 PM UTC

Where did you hear this?  Can you elaborate?

Jan 22, 2016 4:37 PM UTC

It was discussed at the user conference in Nashville last year.

Sorry, no details.

Jan 22, 2016 4:38 PM UTC

And to be clear, I'm not even sure the changes will affect the described situation. I only know changes are planned.

Jan 22, 2016 6:35 PM UTC

So why would you vote down based on no real information?