Recently active
This is a product idea conversion of case 12974199. API extension required to change color of a drawing symbol to the default color of the drawing.
This is a product idea conversion of case 15255035. New API required to access drawing datum targets.
This is a product idea conversion of case 15285337. API extension required to set number of decimal places for a reference dimension.
Please, improve the functionality of ProDtlattachGet so it would return the proper information for currently unimplemented attachments. Judging by our experience, the most used are attachments to axes, cosmetic features and surface silhouettes.
This is a product idea conversion of case 13988445. legacy datums accessibility
This is a product idea conversion of case 13591995. New API required to determine if a geometric tolerance annotation is 'draft' or 'model', because there is no standard way to do that.
This is a product idea conversion of case 15319307. New API required to query positions of a drawing table cells and positions of notes inside the cells.
It often happens that Creo crashes after a specific sequence of Creo API calls with a specific model. And it is not possible to reproduce the crash with an isolated code sample or with a free model that is not covered by NDA. We would like to have an option to send a crash dump (a *.dmp file) so PTC Creo R&D team will investigate it.
It would be great to improve shell feature. PTC explains that there is a limitation with shell feature when exterior corners (round transition) are defined with more than 3 edges and thickness passes the corner from 4 edges to zero edge. https://www.ptc.com/en/support/article/CS323249 It is OK if the corner is defined by 3 edges. Creo can offset the exterior corner from 3 edges to zero. I compared SolidWork 2019 and Creo7 shell features. Have a look at the video and see that SolidWorks allows shell feature where Creo fails. (function() { var wrapper = document.getElementById('lia-vid-V4bjZkajE6J5H4MIz-7rRLvSQPX-D9Cnw400h247r490'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('
This is a product idea conversion of case 15263711. API extension required to set filection filter for set datum tags.
This is a product idea conversion of case 14014485. API extension required to query text style of a drawing set datum tag.
We would like to have TOOLKIT API to change end points of dimension witness lines in the solid and in the drawing.
There should be a way to duplicate a drawing view exactly, including the annotations of that view. Selecting the view and it's annotations and copying and pasting could be a simple solution. Currently there are a few ways to get the view duplicated but the annotations are lost.
We would like to have the TOOLKIT API to get the positions of leader line jogs and create new ones for dimensions, notes, geometric tolerances and custom symbols in the drawing.
This is a product idea conversion of case 12836764. New API required to access bom balloons and its properties.
This is a product idea conversion of case 12895854. New API required to query connection between a model and a drawing custom symbols.
New API required to access roughness symbols owned by a drawing.
New API required to query geometric representation (as set of curves) of text in a sketch feature.
Add ability for use of parameters in the Superscript and Subscript text syntax @+<param_name>@# and @-<param_name>@# This would be very useful for custom hole charts with hole callout notes when certain hole sizes have non-symmetric tolerances. For example the tap drill for a #4 helical insert is a #31 drill, .120" diameter. Allowed minor diameter per NASM spec (rounded to 3 place decimals) is .118"-.125". So the preferred hole callout would be .120+.005/-.002. This uses the standard tap drill and the tolerance range permitted per the NASM spec. When displaying this hole callout on a drawing or model annotation we would typically stack the tolerances (i.e. +.005 over the -.002) in super/subscript. This is currently not possible when the hole sizes and tolerances are entered into the hole chart as parameters, since the Superscript and Subscript syntax above only allows plain text.
Within the native Creo model you can specify a 3D dimension as a so-called inspection dimension or a basic dimension.This property can be interrogated in Creo Toolkit with the use of the API ProDimensionIsInspection and ProDimensionIsBasic. There is also a parameter PTC_DISPLAY_TYPE when interrogating the 3D dimension manually that can hold the values "Basic", "Inspection", "Neither".When you export this model according to STEP AP242 the property "Inspection" is lost in the translation.After importing the STEP AP242 file there is also a parameter with the name PTC_DISPLAY_TYPE which can hold the values "Basic" or "Neither".It seems logical to me to use this parameter to also hold the value "Inspection" as is the case in the native model.
We need API(TOOLKIT or OTK C++) to query whether a datum target object is movable datum target or not in Creo Parametric
For some Pro/Toolkit applications it would be very useful, if they could update their UI depending on the selection the user made in the model. For example if you show a custom model tree, that only shows specific features in a separate dialog and you want to highlight them in your dialog, when the user selects those features in the model. Currently Toolkit provides a similar API with ProSelectExternalhighlightRegister, but those only work for ProSelect. It would be appreciated, if that API could be extended to every modification of the selection buffer or a new API with a similar interface could be provided (i.e. ProSelectionBufferExternalhighlightRegister). That would allow for a much more powerful integration between external Toolkit applications and Creo. Alternatively a simpler API could be provided, that only notifies a Toolkit application, that the selection buffer changed, but reading the full selection buffer on every modification can be expensive and slow in lar
Users should able to get the Default origin (co-ordinate) for those specific 'User Defined-Symbols' which has custom origin.
References used to create a features (extrude, weld, hole, and others) that are later "removed" by another feature, like a cut (machining process), cause regeneration failures because of missing references. This is a common practice when representing the machining features in the assembly's tree. The ideal, would be to save/maintain the references or do the regeneration starting from top to bottom of the model tree, since the references still exist when the feature referenced is created.
Modifying the view display style should only apply to the currently active window. Or, at least make this a config setting which the user can turn on/off. It would be so much better if the view display style setting "sticks" for each window I have open. Changing the view display style for one window should not change the setting for all open windows! It results in a lot of unnecessary clicks when flipping between different parts and assemblies.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.