From: Chris Dubea on
And I got my functionality to work. It's amazing how hard it is to
write code without being able to use the debugger ;>

Thanks a lot.
===========================================================================
Chris
From: Heikki Leivo on
Hello Chris,

> Let's review the debugging issue a bit if we can. I've done this in
> the past but can't for the life of me get this to work.
>
> Can you be MUCH more specific about how to make this work?

Well I dont' know how much specific I can be, but I'll try. You just have a
bug eg. erroneous line of code in your code and you have to fix it, there is
no more sophisticated way than debugging. In your addin class module, find
the function named ConnectToSW. Select the first statement eg. row of code
in the function and hit F9 to toggle a breakpoint on that line. Then hit F5
to start the add-in. Start SolidWorks and the code execution breaks on the
breakpoint, and after that you can run the code row by row by hitting F8.
Select View -> Locals to see the current values of your local variables. Try
to find the row which causes an error, and then fix the code. This process
is called de-bugging. You can also right-click the code and select Toggle ->
Break on all errors, so you don't have to put a breakpoint but instead the
code breaks automatically on a row which causes an error.

Hope this helps!

-h-


From: Chris Dubea on
On Wed, 22 Feb 2006 22:33:28 +0200, "Heikki Leivo"
<heikkidotleivo(a)cadworksdotfi.removethis> wrote:

>Hello Chris,

>Well I dont' know how much specific I can be, but I'll try. You just have a
>bug eg. erroneous line of code in your code and you have to fix it, there is
>no more sophisticated way than debugging. In your addin class module, find
>the function named ConnectToSW. Select the first statement eg. row of code
>in the function and hit F9 to toggle a breakpoint on that line. Then hit F5
>to start the add-in. Start SolidWorks and the code execution breaks on the
>breakpoint, and after that you can run the code row by row by hitting F8.
>Select View -> Locals to see the current values of your local variables. Try
>to find the row which causes an error, and then fix the code. This process
>is called de-bugging. You can also right-click the code and select Toggle ->
>Break on all errors, so you don't have to put a breakpoint but instead the
>code breaks automatically on a row which causes an error.
>
>Hope this helps!
>
>-h-
>

Thanks. I got the debugger and my application working. I'm doing
beta testing (with a few brave individuals) and then I will release my
Custom Property tool on the world!!!


===========================================================================
Chris