Skip to main content
13-Aquamarine
April 17, 2013
Question

Dimensions not moving on first try - just me?

  • April 17, 2013
  • 1 reply
  • 1544 views

All,

Since WF4, I've noticed that quite often (but not every time!), the following happens:

  • I select a dimension
  • I hover over it such that the cursor changes to the "Move" four-way arrow
  • I click and drag - and the dimension doesn't move
  • I try again and it usually moves on the second try.

That was initially under XP x64; it still happens under Win 7 Pro x64. My colleague is currently working in WF5 / Creo 0 under Win 7, and feels that this problem is even worse in WF5.

Have other people noticed this? Have PTC acknowledged it? Does it still happen in Creo 2?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

17-Peridot
April 17, 2013

You have hit a real pet peeve on this one. Even in Creo 2.0, I find myself not grabbing what I clearly intend to grab. Actually, it was worse pre-M040... really bad in M010 where the mouse focus became shifted from the screen click as much as a 1/2" or so. The only way you would know this is through pre-highlighting.

The problem is that we seem to need to pick lit pixels... not a specific bounding box for certain picks. The price for fewer mouse clicks seems to be many more mis-clicks

So for the most part Creo 2.0 M040 is fairly stable about screen location, but actually grabbing what you want still requires a higher level of accuracy than one would think would be required.

13-Aquamarine
April 18, 2013

Well, if the actual pick area to move is limited to certain pixels, then it's really poor UI design to have the mouse cursor change if you're not over one of those pixels.

There seems little point me raising a call as I can only vouch for WF4; but if anyone who's experienced this in Creo 2 would care to start hassling PTC, it might just help...