topic Re: Tips for debugging custom subassemblies in Civil 3D Customization Forum

Tips for debugging custom subassemblies

c__h — Mon, 15 Sep 2008 18:09:00 GMT

I am trying to create a few new subassemblies, but I am having trouble debugging my first one.

Any tips?

When I try to use it, its fails, saying "Unable to execute tool" Message was edited by: honeyman

Re: Tips for debugging custom subassemblies

nzeeben — Tue, 16 Sep 2008 02:40:39 GMT

Corey,

There is almost certainly a problem with your ATC file. They are by and large the hardest part of creating a custom subassembly. The biggest thing to watch out for is that spelling and case count. I would comment out things like input variables while you are troubleshooting, just to get yourself down to the lowest common denominator. I am hoping to get around to creating an xml schema that will be able to verify the atc's against for subassemblies but it hasnt made it to the top of the list yet.
Nick

Re: Tips for debugging custom subassemblies

c__h — Tue, 16 Sep 2008 21:32:43 GMT

Hmm, I can't seem to find any issue.

It seems to be not registering properly. It imports (I am using a pkt file), but I get none of the usual options with a right-click (help etc) and the Unable to execute error when trying to use it.

I have been comparing it to some other ones that work, and I can't seem to find an errors.

Also, Nick, where can I get a list of these resource strings, such as used for logical names and such (oParamLong.Displayname = "8090" )

Re: Tips for debugging custom subassemblies

nzeeben — Thu, 18 Sep 2008 18:59:55 GMT

Can you email me the pk tfile and I will take a look at it?

As for resource strings I dont have a list but you could skip them entirely as you dont likely need to translate your code.

If you want to see what they are you can use resource hacker to see the ids in the resource dll.

Re: Tips for debugging custom subassemblies

nzeeben — Fri, 19 Sep 2008 14:01:48 GMT

Corey,

I looked at the atc file you sent, it appears you changed the guid for the stocktoolref, if you do that, it will not work. All subassemblies use the same stocktoolref GUID.

Each SA needs its own unique item ID GUID.

Re: Tips for debugging custom subassemblies

c__h — Fri, 19 Sep 2008 17:06:10 GMT

I didn't know that! Thanks!

Enjoy your trip! Message was edited by: honeyman

Re: Tips for debugging custom subassemblies

c__h — Fri, 19 Sep 2008 19:59:25 GMT

Ok, another question.

I now have a long list of folders in my "Imported Subassembies" folder.

Can I just delete those folders? Or do I have to unregister them too?

Oh, and also having trouble with the help file. Its just a simple html but it doesn't work when launched from the palette. It says "Help operation failed" Message was edited by: honeyman

Re: Tips for debugging custom subassemblies

nzeeben — Fri, 19 Sep 2008 20:03:15 GMT

You can delete them.

Help the only formats supported are pdf or chm(compiled help menu)

Re: Tips for debugging custom subassemblies

c__h — Fri, 19 Sep 2008 21:25:18 GMT

Can't get a PDF or doc to work either.

Any example ATC's that don't use a chm?

Thanks for all your help. Message was edited by: honeyman

Re: Tips for debugging custom subassemblies

nzeeben — Sun, 21 Sep 2008 15:24:18 GMT

If you look at the contents of the new pkt files we released via sub center they have pdfs defined.

Re: Tips for debugging custom subassemblies

c__h — Tue, 23 Sep 2008 00:04:11 GMT

The atc for all of those point to a chm file. But its ok, I got a chm file to work, so I will go with that.

Thanks for you help.

I finally got this thing working.