Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo 3 & Chrome networking with PDMLINKArchived

Networking problem when using Creo 3 with PDMLINKChrome is built to use the IE network settings. In Creo 2, I can set Firefox network settings up in a way to best make use of the network and leave IE alone to the corporate IT types (here they force the use of a proxy config script). How do I do that going forward with Creo 3 which is going to use IE or Chrome? PTC has taken functionality away that enables alternative network browser settings that make their toolset run better.This issue is due in part to a known Microsoft IE issue (http://support2.microsoft.com/kb/262981)The resolution provided by Microsoft does not work if you have to use a proxy config script.I already figured out Chrome using the command line to set the proxy server and proxy server bypass in advance of getting Creo3 and installing it. Didn’t see how that was going to be usable inside of Creo3 unless PTC is not bundling Chrome as it did with Mozilla/Firefox. If PTC is using the external Chrome implementation, will CREO3 allow the command line to be altered to include the proxy statement and bypass? If PTC does bundle a Chrome implementation like they did previously with Firefox, the same question about being able to configure the proxy and bypass is applicable.The use of Google Chrome Extensions are also a question, if we use them to correct/skirt this issue, will PTC support their use or tell us to turn them off if we’re having any issues. A lot of this again depends on PTC’s implementation plan, is PTC bundling Chrome as done previously with Firefox?Anyone else have this sort of problem?

Customization commands inconsistentArchived

Clicking on the menu on the Quick Access Toolbar brings up a menu allowing you to turn on/off the commands on it. To customize it, there is a command "More Commands..." which is, first of all, not clear; it should instead be something like "Customize" or "Add/Remove Commands". But what doesn't make sense is that by selecting it you get to the "Options" menu, but the "Customize Ribbon" option is seleted, NOT the "Quick Access Toolbar" option.If I right-click on any place on the ribbon, I do get an option to "Customize Quick Access Toolbar.." (which does bring up that option), but why isn't it the option to "Customize Ribbon" in that case? In the Options menu, toward the bottom, there is a drop-down menu next to "Customization:" with the options "Reset" and "Reset All". But it isn't clear how to actually execute those commands. It would be much more consistent to have two buttons instead. And when customizing the Command Mini Toolbar, there are buttons for "Reset" and "Reset All". Similarly, there are buttons for "New Tab" and "New Group", but "New Element", "Menu", "Split Menu", and "Separator" are selections from a drop-down menu-why are those done differently? And in that case, and the case with the "Reset" and "Reset All" commands, how is someone supposed to know that they need to select the menu and then select the command-especially when the command that they want is already being displayed? When customizing the ribbon, you can choose commands from "Available Command Groups", "All Tabs", "File Tab", and "Custom Tabs & Groups". But when customizing the Quick Access Toolbar, the options are "Available Command Groups" and "Ribbon Tabs". And when customizing the Command Mini Toolbars, the only option is "Available Command Groups". Why should they be different?

Feature names with special characters (=, - and +) to document Reference DesignatorsArchived

In Creo Parametric it is possible to enter a text string in the Feat Name column in the modeltree for each component in an assembly.This information will automatically be added to the WTpart structure in PDMLink as information in the Reference Designator field.Unfortunately it is not possible to enter special characters (e.g. =, - and +) in the Feat Name field.The Reference Designator can be found in PDMLink in the Occurrences tab.Please make it possible to enter special charcters in the Feat Name column.In this way PTC would follow international standards for this field since 1996.IEC 81346-1:2009(en) Industrial systems, installations and equipment and industrial products — Structuring principles and reference designations — Part 1: Basic rules (It has been known since 1996 as IEC 61346)ISO 7573:2008(en) Technical product documentation — Parts lists (Referring to 81346)ISO/TR 19033:2000(en) Technical product documentation — Metadata for construction documentation (Referring to 81346)ISO/TS 16952-10:2008(en) Technical product documentation — Reference designation system — Part 10: Power plants (This is RDS-PP, build on 81346)ISO 1219-2:2012(en) Fluid power systems and components — Graphical symbols and circuit diagrams — Part 2: Circuit diagrams (Referring to 81346)In Electrical IEC 61082-1:2006 Preparation of documents used in electrotechnology is the one to follow

Enhancement for Creo View and ECAD Adapters InstallationArchived

I have recently had to help a company End User install and configure Creo View Client (including ECAD Adapters) and the ECAD Validation packages for use in Creo Parametric 2.   While the installation of all components went smoothly enough, there was one glaring inconsistency that I feel needs to be mentioned and hopefully addressed.  During the first installation phase, the Creo View Client, an additional installation took place for comething called Creo View ECAD Adapters.  While the overall installation allowed me to change the default install folder location (which my company does routinely) this component was not installed at my chosen location but rather under C:\Program Files\PTC\CCreo 2.0\View ECAD Adapters.  Thus our internal desire to have all of our related tool components installed into a common location was thus defeated.  The second component (ECAD Validate), installed from the same Setup program, also asked for where it should be installed and did so.   In my humble opinion, if you are going to ask me where I wish to install something, then the least you should do is respect that and place the software where I asked it to be placed.  I could see no way to defeat this behavior in the installer.  If there is something I missed, or if there are command line installer switches I can use when automating such an installation, that would be fine.  But I saw no opportunity to intervene in this process when runngin from the Setup program UI.  We routinely have to install for many hundreds of users, and have a Global support staff who need to know things are "just so" in order to be able to support these tools.  The bahavior I've mentioned here is one of the many little factors that make things harder for us.