Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Incremental Geometry ImprovementsArchived

I have a board from a vendor with hundreds of components in one .prt (not to messy up our database). The components are broken up into a few dependent and incremental geometry features in the model tree. I've had to edit an Incremental Geometry feature to get one of the components to solidify. I would like to use the Import Data Doctor, which can't be done with an Incremental Geometry feature, only an independent or import geometry features. In order to get an incremental to a dependent, I had to deselect the ATTACH feature in the Incremental Geometry dashboard and then collapse the incremental geometry feature with another feature. Once that is done, the feature is now Independent. HOWEVER. when you deselect ATTACH, it does not solidify the surfaces in the feature. When converted into an independent feature, it still will not solidify the feature, EVEN when you select the solidify button on the dashboard. The ONLY way I was able to get this to work was to use the solidify feature for EACH component quilt and then collapse all of this into the independent feature. Of course this one feature had over 50 components, so I had to create 50 solidify features and then collapse them back in. All of this, just to fix one of the components in the old incremental geometry feature. So... after this long background... I believe Creo should:Allow the Import Data Doctor from an incremental geometry featureAllow the easy conversion from an incremental geometry feature to an independent WITHOUT requiring to deselect ATTACHAllow for an independent Geometry to always try to solidify the feature, when the solidify toggle is selected, even when it used to be an unattached incremental geometry feature.Thank you!

Properly cascading keyboard shortcutsArchived

Hello,TL;DRShortcuts and all_filer_project_dir files (perhaps others) should cascade properly through different customization levels rather than squashing lower-precedence customizations.I've just been customizing v19 Creo Elements/Direct at the site and user levels, and I noticed that most of the customizations cascade in a well-ordered way, with a precedence of factory/corp/site/user, which works great. But the shortcuts (e.g. sd_shortcuts.acc) and the all_project_filer_dir files do not seem to cascade this way. They are in the category of “first file found in…” rather than “all files found in,” as described in the startup order documentation. This is problematic because a user that adds a SINGLE keyboard shortcut to their user level (say through the Customize menu) has blocked themselves from seeing ANY changes to keyboard shortcuts at the site level.The idea is that keyboard and project directories should cascade in a similar fashion to all the other features. Keyboard shortcut additions (and removals!) should be recorded at the user-level, without stomping lower precedence keyboard shortcuts.Here is an example.Existing functionality:Suppose the user has not modified any shortcuts so there is no user_customize/sd_shortcuts.acc, and Site/sd_shortcuts.acc has these shortcuts:("CTRL E" :command "Extrude")("CTRL M" :command "Mill")("CTRL P" :command "Punch")If a user changes the keyboard shortcut for "Punch", user_customize/sd_shortcuts.acc is created with the following shortcuts:("CTRL E" :command "Extrude")("CTRL M" :command "Mill")("ALT P" :command "Punch")Despite the fact that the user only intended to define the Punch shortcut, he just captured ALL of them. Now suppose a shortcut is added at the site level:("CTRL E" :command "Extrude")("CTRL M" :command "Mill")("CTRL P" :command "Punch")("CTRL S" :command "Stamp")The user will not see the effects of this, because user_customize/sd_shortcuts.acc, rather than complementing and (where collisions occur) overriding shortcuts in Site/sd_shortcuts.acc, squashes all of them.Proposed functionality:When the user changes the keyboard shortcut for "Punch", user_customize/sd_shortcuts.acc should instead be created with only the following:("ALT P" :command "Punch")The only problem now is "How do you know if a user wants to remove a keyboard binding?" Instead of checking for its absence in user_customize/sd_shortcuts.acc, just record removals in that file:("CTRL P" :command "Punch" :removal t)Obviously for this to work the loading mechanism can no longer simply take the highest-priority shortcuts file and use that. It has to integrate the shortcut files at various customization levels (as it does with other things IIUC) but that doesn't seem too difficult.Regards,Rich KinderKeysight Technologies