The TCs are working on providing feedback/information to PTC on Measure Tool in PRO/E.Please send any feedback to the following questions...Thank you for your time and feedbackDo you use the existing measure tool?If yesWhat do you like about it?What could be improved?What types of measurements are you performing? For what purpose?How is this information used? Does this information get passed downstream? In what format? (email, parameter in the model, in a table on a drawing, etc)Would it be useful to display this information in a persistent note, annotation or other type of feature?If no, why not?Is it too difficult to use?Is it not necessary for your job function?Any additional comments or information on how the tool is used is welcome. The more details we get the better we can design the new User Interface.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.

Thank you to everyone who has replied to this thread! I've been pleasantly surprised at the quantity and consistency of everyone's feedback, which makes it easier to prioritize what needs to be done. Here are the underlying themese that I've observed: Make the measurements intelligent (i.e. If you select a surface you probably want the surface area and perimeter, if you select a curve you probably want the curve length, if you select two edges you might want the minimum and maximum distance, etc.) the current tool returns a single value which may not be what you were looking for Today when measurements are saved, they are "hidden" and not easy to access (compared to annotations which show int he model tree). I envision a history of measurements that have been taken in session that are easily copied, transferred to a parameter or perhaps even stored in an annotation feature. Of course we will have to see if any of these options are possible. If measurements are saved, they cannot be moved and their appearance cannot be modified. Again, I would like to see some of the same capabilites tha are available for annotations applied to the measure tools. Of course there several other items that will be improved over time, but I see the above points as the major ones to address first. Rosemary Astheimer PTC Product Manager, AnyData Adoption

J

jnelson

14-Alexandrite

Question

Measure Tools

Forum|Forum|15 years ago
April 23, 2011
29 replies
10608 views

The TCs are working on providing feedback/information to PTC on Measure Tool in PRO/E.

Please send any feedback to the following questions...

Thank you for your time and feedback

Do you use the existing measure tool?

If yes

What do you like about it?

What could be improved?

What types of measurements are you performing? For what purpose?

How is this information used? Does this information get passed downstream? In what format? (email, parameter in the model, in a table on a drawing, etc)

Would it be useful to display this information in a persistent note, annotation or other type of feature?

If no, why not?

Is it too difficult to use?

Is it not necessary for your job function?

Any additional comments or information on how the tool is used is welcome. The more details we get the better we can design the new User Interface.

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.

General

Show previous replies

A

A.DelNegro

1-Visitor

A further improvement to #1… Why do I need to add a column to show the value anyway? If I’m adding an analysis feature, one of the main reasons I use this is to monitor this value. Why not display the value in the name of the feature say like… ANALYSIS_DISTANCE_1 [3.2543] ?? Or maybe even give me a RMB click that would show me the value of the feature? I personally don’t usually show any columns other than the model tree. I add columns when I’m modifying parameters in my assembly drawings but that’s pretty much it. It seems a waste of screen real estate to add a whole column, just to show the value next to the one or two features.

Tony

J

JonathanHodgson

13-Aquamarine

I commented on this on PlanetPTC some while ago:

D

DeanLong

1-Visitor

And while we are at it...

The Analysis tool in general, Quick Vs. Saved specifically. Whymust all the Qucik values go away as soon as an analysis is completed? If I wanted to save it, I would choose Saved, but I don't want a saved analysis. However in order to see what I want, I mustchoose Saved... (why isQuick the default value in the flyout???). So, I run the analysis and it and then goes away. Useless.

In order tosee the values I want I am forced to chooseSaved Analyses, which then requires me tochoose the Analysis tool again, then View Saved Analysis (which is hidden by the way), then forces me to choose unhide to see the values I wanted to see eight clicks back. Huh?

For the life of me, I cannot understand the logic that was employed with this functionality. Please make it simple.

D

dgschaefer

21-Topaz II

It's stupid UI more than anything. If you click the glasses button,
it'll run the analysis and show you the results. If you click the green
check, it's like saying done and it dismisses the dialog. Why it runs
the analysis again before dismissing is beyond me. I just use the
glasses (to run the analysis) and the red X to close, don't bother with
the green check button.

Nearly every user that encounters that UI does what you do and can't
figure out why. I can't believe that any Pro/E user actually used and
approved that dialog before it went into the software.

Doug Schaefer

D

DeanLong

1-Visitor

Yeah Doug...I guess it's just a caseof the Old Dog (me) trying to learn (rather "notice") the new tricks. I feel a bit foolish as I have been on the Wildfire trail for 6 years! Sad isn't it?

Can you hear the Gray Matter hardening?

A

Anonymous

Thank you to everyone who has replied to this thread! I've been pleasantly surprised at the quantity and consistency of everyone's feedback, which makes it easier to prioritize what needs to be done.

Here are the underlying themese that I've observed:

Make the measurements intelligent (i.e. If you select a surface you probably want the surface area and perimeter, if you select a curve you probably want the curve length, if you select two edges you might want the minimum and maximum distance, etc.)
- the current tool returns a single value which may not be what you were looking for
Today when measurements are saved, they are "hidden" and not easy to access (compared to annotations which show int he model tree).
- I envision a history of measurements that have been taken in session that are easily copied, transferred to a parameter or perhaps even stored in an annotation feature. Of course we will have to see if any of these options are possible.
- If measurements are saved, they cannot be moved and their appearance cannot be modified.
  - Again, I would like to see some of the same capabilites tha are available for annotations applied to the measure tools.

Of course there several other items that will be improved over time, but I see the above points as the major ones to address first.

Rosemary Astheimer

PTC Product Manager, AnyData Adoption

C

cordeneaux

3-Newcomer

OUCH ... she said "ribbon"
Especially, since that's worked out so well in drawing mode.

W

wattsteam

1-Visitor

Please DO NOT make the measure tool a ribbon. The ProE drawing ribbon interface is awful, please don't ruin measure tool the same way.

Jeff Dayman

J

jnelson

Author

14-Alexandrite

All,
IF you are your bothered by the Ribbon Interface from Wildfire 5, it is understandable.

However, the Ribbon Interface in CREO 1 is completely revamped, and totally customizable.

I too was disappointed with what WF5 had offered. However, I am completely satisfied with the Ribbon in CREO 1 and looking forward it.

Joel Nelson
PTC/USER Sheetmetal TC Chair

[cid:image001.jpg@01CC065A.54D88100]