cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Creating ProToolkit Application

cummins_beproje
1-Newbie

Creating ProToolkit Application

Hello All,
I made an application using ProToolkit Wildfire 2.0. But after registering its DLL in Pro/E and clicking on our menu button, Pro/E closes automatically. So what can be the problem? Please reply.

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.
4 REPLIES 4

Do you get any error messages in the std.out file? Mine usually shows up
in the same folder that I use as my startup/working folder. That may
give you an idea.

The other thing that I can think of is that I have seen this type of
behavior when I have a variable that doesn't work correctly
(insufficient memory allocation or something like that). I would
recommend writing a log file (something I do for almost any program I
write these days) with variable values and checkpoints in the code so
that you know where it dies.



Wade Wyss

CSU Special Project 04341
Support for TMM 02994



Cogito sumere potum alterum!!

This can also happen when you have two entries in the registry file the
same. The protk.dat file loads from several default locations and you
can define more in the config.pro file. If you happen to have two names
the same in the combined set of registry files Pro/E will go down.

W.C. (Bill) Bowling
Associate Technical Fellow
Pratt & Whitney Rocketdyne
Mechanical Design
Engineering Design Services (D902)(MS: FB24)

--- cummins_beproject@rediffmail.com wrote:
>
> I made an application using ProToolkit Wildfire 2.0. But
> after registering its DLL in Pro/E and clicking on our menu
> button, Pro/E closes automatically. So what can be the problem?

Another technique to help diagnose the problem is to
recompile your DLL application as an EXE (spawn mode),
if possible.

Sometimes, spawn mode applications report problems better
than DLL's. When problems occur, they usually don't take
down ProE either.


Marc



















Check for uninitialized variables!

I recently had the exact same thing in WF2, where my DLL would make
Pro/E crash, yet the EXE ran ok. I tracked it down to the code I wrote
for making the menu buttons available in certain model modes (eg,
drawings). I had called ProMdlCurrentGet(&model) followed by
ProMdlTypeGet(model,&mdl_type) call without checking the return status
of ProMdlCurrentGet. The DLL worked again after I added a return status
check:

status = ProMdlCurrentGet(&model);
if (status != PRO_TK_NO_ERROR) {
return(ACCESS_UNAVAILABLE);
}
ProMdlTypeGet(model, &mdl_type);

I was able to get away without checking in Wildfire, but not Wildfire
2.0.

Hope this helps.

Chris Figura
Prin. Design Automation Engineer
Medtronic, Inc.


Announcements
Attention: Creo 7.0 Customers
Please consider upgrading
End of Life announcement here.

NEW Creo+ Topics:
PTC Control Center
Creo+ Portal
Real-time Collaboration