Skip to main content

Filter by idea status

Filter by product

6851 Ideas

More flexibility for ISAM scenariousNew Idea

Related to case C14766684 the following idea:   In the communication between the ILM rich client and the ILM server via a a virtual host junction (VHJ) of an ISAM instance, it is currently necessary that the rich client accesses the same port and URL, that is configured in the ILM server in the properties "mksis.secure.port" and "mksis.hostname".   ILM client ------> ISAM VHJ (running on hostnameA:portA) ------> ILM server (running on hostnameB:portA)   This is necessary, because the server communicates in the payload of responses the target URL incl. port, that the client shall access after the first request.   On the other hand sends the client in every request the "hostnameA:portA" in the http host header to the ISAM server (for identifying the VHJ) and the ISAM server sends the same host header in the requests to the ILM server.   That means, that the ILM server has not only the possibility to send the target URL incl. port based on the server configuration but also, as an alternative, based on the http host header (which is already approved for correctness, otherwise the first request would not have reached the ILM server).   Please implement (in the use case of ISAM usage) the possibility and option, to take the relevant information for the target URL incl. port (that the server communicates to the client) not from the configured properties of the server, but from the send (by client + ISAM) host header.   This would enable the flexibility/possibility to uses other scenarios with e.g. different hostnames and/or ports on client and server side.   This would be also valid for the thin client.  

Improve Creo Schematics CrosshatchingArchived

Creo Schematic crosshatching should be improved to where the overall feel should be similar to existing crosshatching performed in drafting programs and minimize the number of clicks to perform the actions.     The following statements are based on my experience in Creo Schematics 2.0 M020:   Closed geometry should pre-highlight for selection When you go to create a crosshatch the closed geometry does not pre-highlight. Single click to select closed geometry You have to double click the closed geometry to create the crosshatch, this should be a single click. Ability to click anywhere on the crosshatch You cannot always click anywhere on the crosshatch, it appears as those the selection area is within a certain distance of the closed geometry inside and outside the shape, and sometimes in the middle. Right-Click modification of crosshatch To modify the crosshatch you cannot select, right-click, properties (the option is greyed out). To modify the crosshatch you have to select "Modify Crosshatch" from the menu. Without pre-highlighting you have to select the crosshatch area which as mentioned above is not on the crosshatch lines. Then through the right-click menu, you can click Properties, then change the angle, spacing, etc. This is way to many steps. It should be a simple select, right-click, properties. Ability to Pre-select geometry prior to menu command You cannot pre-select closed geometry to create crosshatching, or crosshatching to modify the crosshatching through the menus. Additionally a fill option would be ideal to create solid features rather than relying on close crosshatching.     If I'm missing something please feel free to add comments.

Need WYSIWYG export of CAD linestyles to PDF and PVZ.Archived

Currently ProE/Parametric have "use_software_linefonts" config.pro option to force WYSIWYG plotting of linestyles into hardcopy.  The linestyle you use in the ProE feature or drawing will be the linestyle you see on the hardcopy.  Unfortunately, there's nothing similar for the "Export" function, meaning that neither PDF nor PVZ can reproduce the linestyle used inside of ProE.  CAD users can choose from many different linestyles, but this information is lost during the conversion to PDF/PVZ.  We wanted to migrate from AutoCAD to ProE for manufacturing overlay design, but are struggling to do that without WYSIWYG PDF output.   For PDF, I'm using the old fashioned workaround of dedicating a specific drawing color to a specific linestyle, and then hard-coding the dashing through a pentable assignment that matches my needs for the one specific linestyle.  This approach is extremely inflexible and limited.  It requires consistent upfront training of users to avoid using that specific color for anything unless they desire a dashed line.  Users ALL need to understand that their PDF and PVZ will not match their ProE model and drawing...   Creo View Adapter has no workaround that I'm aware of, since it does not allow for the same type of configured linestyle via pen mapping, so there's no way to get a specific linestyle displayed in the PDMLink viewable.   My ideal case would be to either always export as-is linefonts or to implement something like "use_software_linefonts" that could be leveraged by both automated PDF export and Creo View Adapters.   Example below shows ProE drawing.  Model "sketch" features had used "dashfont_s_s" linestyle for all horizontal lines shown dashed here.  User is happy with drawing display within ProE window.  Notice different colors assigned here to demonstrate the default condition and pen mapping workaround.   PDF example below uses pentable to give acceptable short-short dashes as intended by using "dashfont_s_s" in ProE feature.  Red arrows highlight manually changed line colors to match "highlite_color," drawing a specific mapped pen assignment: pen 4 thickness 0.005 in; pattern 0.08 0.08 in; highlite_color   Yellow arrows show default "section" line color, still giving unacceptable default long-dash result.