chook source code

[Duckman]

is there any way to get the source code for the chooks included with mastercam?

 

i'm trying to learn the api, but there's so much it's overwhelming...

thx

[Bullines]

You can always ask and beg for source

[Guest CNC Apps Guy 1]

You mean I can beg too? I've been wanting to ask for the source for a C-Hook or two because I'm having some problems with one I'm putting a Windows Dialog Box on. Asphere is what I want to see.

 

Should I beg to PDG?

 

[ 06-12-2002, 12:35 AM: Message edited by: James Meyette ]

[Duckman]

please please please pleae pretty please can i have source code!!!!???? to anything!!!! i need to LEARN!!!

 

thx! : )

[Bullines]

If something isn't in the SDK, then it's not there at all. I know it's a pain to search the DOCs and Hs ; I'd love a well made CHM or object heiarchy listing . PDG has been good to me when I needed answers to "what would I use from the SDK if I want to...?" type questions. I'm not sure how responsive he would be to C++ syntax, UI design or programming methodology questions since he is usually quite busy. I don't mind fielding those types of questions, though

[ProductDevelopmentGuy]

The TEST*.C files that we ship with the C-Hook kit are all that we supply. I admit that it's probably not enough. We'll continue to work on it.

PDG

[Guest CNC Apps Guy 1]

Thanks PDG. The more info (without giving away the store) the better since I'm a novice too.

 

Bullines, thanks for your help.

[bryan314]

First off I wanted to add my "me too" to getting a look at some chook source code. Including more examples in the sdk would be great.

 

I'm sure there has been many times where I've reinvented the wheel writing chooks where the developers at Mastercam probably did it better a long time ago.

 

Bullines wrote:

quote:

---

If something isn't in the SDK, then it's not there at all.

---

That's not entirely true. I've noticed a few items either missing by accident or by design. You really have to read through the header files since not everything listed in the documentation.

 

For example:

Listed in m_draft.h but not in the documentation there are some really useful functions for reading Mtable Items (note text) from external mastercam files.

mTableReadStart

mTableReadItem

mTableReadEnd

 

And some items are just not there. Of the various file types, only a portion have their path prefix listed. You can look through all the docs, example files, and all the headers files and you won’t find how to get the STL file path. Nada, zip, nothing.

 

But it you add

EXTERN char *stl_prefix;

patterned after the other prefix's, it works fine.

 

Hopefully added documentations is in the works.

 

Bryan