Skip to main content
1-Visitor
Mar 6, 2023 9:39 AM UTC
Acknowledged

Utility function ProUtilErrPrint() should support all error codes defined in ProToolkitErrors.h

Related products:Creo Parametric

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.

The organization where I work is in the manufacturing industry.
In the organization I am responsible for the CAD and PDM system administration as well as for the Toolkit development.
I support about 300 Creo Parametric users.


2. What version of Creo Parametric are you currently running?

We are currently working with Creo Parametric 7.0.10.0.

3. Description of the idea:
The error codes are ultimately only integer values, since ProError is of the enumeration type.
For debugging purposes, such as output in the Creo message area or log files, it is often very helpful to have meaningful names (strings) instead of just numbers.
Here, the ProUtilErrPrint() utility function provided by the Toolkit installation (found in the file \protk_appls\pt_examples\pt_utils\UtilError.c) could be very useful.
Unfortunately, this function supports only 18 of the more than 80 existing error codes defined in the header file ProToolkitErrors.h.
Of course, a simple workaround would be to create a corresponding function yourself.But our corporate strategy is to always use as much of the standard as possible before customizing.
Therefore we would prefer the existing function ProUtilErrPrint() to be extended accordingly and kept up to date!"

 

Cross reference:

This idea is a result of PTC article CS387353.

2 replies

1-Visitor
Mar 6, 2023 10:02 AM UTC

Unfortunately, something must have gotten mixed up here and the cross-reference should be at the very end.
And the last part of point 3 should read as follows:

 

"[...]
Of course, a simple workaround would be to create a corresponding function yourself.
But our corporate strategy is to always use as much of the standard as possible before customizing.
Therefore we would prefer the existing function ProUtilErrPrint() to be extended accordingly and kept up to date!"

 

@PTCModerator, could you please correct this accordingly?

Mar 6, 2023 10:06 AM UTC
Status changed to: Acknowledged

Hi @DomenicLaritz!

Thank you for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

 

I have also edited your idea, as requested.