Toolkitters,
I've written a StartPart program recently that the users really like.
It's way more functional than a mapkey Startpart. However I have
stumbled across a sticky issue.
The program uses the function ProMdlStartAction, with the description:
Type for callback function for notification option PRO_MDL_START. The
function is called after the user selects OK on the New dialog, if the
option "Use default templete" is unselected, and the notification has
been defined by a call to ProNotificationSet(). The callback replaces
Pro/ENGINEER's interaction by which the user selects the start-part and
defines its parameters.
The startParts I customized are for Parts, Assemblies, and Drawings.
Problem is that for several of the other types of new objects such as
layouts and Formats, when you select that subtype, it greys out the
"Use_Default_template" box, so you are automatically kicked into your
custom startpart routine. I have nothing in there for these types,
because it seems illogical to define templates for formats and layouts,
because they are sized on the fly, and to me a format is a template.
Now when users try to create one of these types nothing happens. They
have to use the aux. apps menu to stop my startpart dll so they can get
back the original Pro/E file, New interaction.
I'm curious as to how anyone else who has used ProNotify
w/ProMdlStartAction has handled this dilemma. Is there something I'm
not seeing?
Thanks,
Mark Steffke
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.
