Skip to main content
P
ppotabatti1-Visitor
1-Visitor
May 16, 2016
Solved

I am trying to create a tapped hole using toolkit. I am clueless to what should be the data value for element PRO_E_HLE_CRDIR_FLIP ?

  • May 16, 2016
  • 1 reply
  • 1373 views

cr_dir.png

I am trying to create a tapped hole and following the user's guide of toolkit.

The error I got after compiling my code is: "PRO_HLE_CR_DIR : undeclared identifier"

How can this problem be solved? Can anybody help?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by GabrielZaha

PRO_HLE_CR_DIR is a enumeration. You need to use one of the enumeration values. For example:

value_data.v.i = PRO_HLE_CR_IN_SIDE_ONE

The enumeration is defined in ProHole.h:

/* PRO_E_HLE_CRDIR_FLIP */
typedef enum pro_hle_cr_dir
{
  PRO_HLE_CR_IN_SIDE_ONE = -1,     /* Std/sketch hole creation in side 1 */
  PRO_HLE_CR_IN_SIDE_TWO = 34      /* Std/sketch hole creation in side 2 */
}ProHleCrDir;

1 reply

G
GabrielZaha14-AlexandriteAnswer
14-Alexandrite
May 17, 2016

PRO_HLE_CR_DIR is a enumeration. You need to use one of the enumeration values. For example:

value_data.v.i = PRO_HLE_CR_IN_SIDE_ONE

The enumeration is defined in ProHole.h:

/* PRO_E_HLE_CRDIR_FLIP */
typedef enum pro_hle_cr_dir
{
  PRO_HLE_CR_IN_SIDE_ONE = -1,     /* Std/sketch hole creation in side 1 */
  PRO_HLE_CR_IN_SIDE_TWO = 34      /* Std/sketch hole creation in side 2 */
}ProHleCrDir;
    P
    ppotabatti1-VisitorAuthor
    1-Visitor
    May 18, 2016

    Thank you Gabriel very much. It worked. As you might have guessed I am new to coding and learning toolkit. Your help is very much appreciated.

    Terms & ConditionsCookie settingsAccessibility statement