Visual C++ Version 8.0

[Jure Klemencic from Camincam]

Hi!

 

I would like to ask whether it is possible to develop C-hooks for Mastercam MR1 by MS Visual C++ Version 8.0 (Express Edition)?

 

And is it OK to use .NET Framework Version 2.0?

 

I couldn't compile a project since I don't have windows.h file. And I couldn' make CHook Wizard work.

 

Thank you in advance!

[Clay Walnum from CNC Software]

Once we get MR2 out the door, I will be looking into what's required to develop C-Hooks and NET-Hooks under Visual Studio 2005. Stay tuned! (And, in the meantime, if you come across any interesting solutions, please pass them along.)

 

--Clay

[Chad 73]

Ehh-HMMM, Ummm MR2 is released.

Is this being looked in to now?? I'm interested to know what i should be using when writing a c-hook. I am just starting to learn the language(C++).

[Pete Rimkus from CNC Software Inc.]

MR2 was built with VS2003 (a.k.a v7.1).

X2 will be built with VS2005.

[wire123]

So, if I buy v7.1 now so I can upgrade and use my c-hooks now, will I be able to use 7.1 for X2 as well?

Would/should the C-hook continue to work in X2?

 

Thanks

 

Cliff Wire

Roll-Kraft

[_]

Yeah,I have VS2003 and VS2005,

I want to know which version of Viasual Studio I should use for compiling C-Hooks fo X2.

 

I'm testing my chooks under X2 beta now,

and I found some of them did not work.

(with messages 'the appropriate Mastercam .NET Support dll could not be found.' 'Unknown file type')

 

so, I compared the difference between them,

and it seems that chooks which using MCDialog class do not work.

and I converted all 'MCDialog' => 'CDialog'.

(and m_version thing..)

 

 

I know I should use X2 SDK,but it is not in my hand yet. just curious..

[Jon Griffin CNC Software]

We at CNC are using VS2005 to compile our X2 chooks. This is the plan going forward as well. MR2 was compiled with 2003, but we made the switch a couple of months ago.

Substantial work has been done behind the scenes on the interface since then, and no effort is being made to be backwards compatible with VS2003 (it would be pointless). I would not be surprised if MCDialog was giving you trouble in VS2003.

 

Personally, I would suggest moving to VS2005, and the X2 SDK, before releasing any chooks for X2. It'll save you a number of headaches.

 

Best of luck,

[_]

Thank you.

 

I'll move to VS2005 before X2 release.

thanks a lot.

[Takashi Sato from Ai Solutions.]

Yes, I have downloaded X2 SDk from dealer site.

 

And I could compile my chook for X2 successfully!

There are a lot of changes regarding UI Control class,and a lot of compile errors like 'include file not found'..

So I commented them out //

quote:

---

C:mcamx2sdkm_core.h(143)://#include "interfacescoreToolListBoth_CH.h"

C:mcamx2sdkm_mastercam.h(26)://#include "interfacesguiMastercamDoc_CH.h"

C:mcamx2sdkm_matss.h(12)://#include "interfacesmatssSimulateThread_CH.h"

and more...

---

[markov]

I have also installed X2 SDK, and although I have not tried to recompile my old C-hooks, I tried creating a new one using the wizard. I found ChookWizard.vsz file in the SDK directory and copied into VCvcprojects. I also copied the icon ChookWizard.ico from the old SDK into the same directory. It now appears in the new project creation menu, and the wizard can start, but when I press "Finish" it crashes Visual Studio. Has anybody made the wizard working?

 

Thanks,

Marko

[Takashi Sato from Ai Solutions.]

The wizard working is not working under Visual Studio 2005 for me..

So I use VS2003 and re-open it with VS2005 for now.

 

however I have to change include paths and add uicontrol.lib etc..

[markov]

I can not compile even existing C-hooks. UIEdit class from "interfacesuictrlsUIEdit.h" has a member of an undefined type HTHEME. Do I have a wrong version of the SDK or what?

 

Marko

[Takashi Sato from Ai Solutions.]

You have to add this line in stdafx.h.

code:

---

 #include <Uxtheme.h>

---

[Zerren Gedeon]

markov,

 

Microsoft changed the way Wizards are done from VS2003 -> VS2005, so the "old" CHook Wizard will not work with VS2005.

 

To update your CHook project so that it will compile using VS2005, you need to make the changes shown here

to add the needed items for the 'UI' stuff.

[markov]

Thanks,

 

This confirms my suspicion about broken SDK: I am missing the file Uxtheme.h, as well as CommCtrl.h and tmschema.h from Zerren's post! Where did you get your copy (of SDK or just these files) from?

 

Marko

[Takashi Sato from Ai Solutions.]

Did you install Platform SDK?

[markov]

Sorry, I thought these were Mastercam files, I did not look into Platform SDK. I did not even try to compile with those "#include"s when I did not find the files in the X2 SDK! I shall try it as soon as I get the chance, but I think it will be OK.

[M. Harnad CNC Software]

The C-Hook wizard had to be re-written for Visual Studio 2005 because Microsoft changed the underlying architecture. It was completed about the time of X2 being finalized. Unfortunately, it did not make the CD. I think the plan is to make it available for MR1. However, you may want to petition to make it available from the Mastercam download site.

[M. Harnad CNC Software]

To all C-Hook developers migrating from Visual Studio 2003 to Visual Studio 2005.

 

It is recommended that you apply the following changes to existing C-Hooks when migrating to VS 2005.

 

1. Ensure that the all predefined version macros (ie. WINVER, _WIN32_WINDOWS, etc.) are set to at least 0x0501. Failure to do so may result in unpredictable results.

 

2. Add the following three includes to your stdafx.h file:

 

#include "tmschema.h"

#include "CommCtrl.h"

#include "Uxtheme.h"

 

In order to use the above includes, you must have the latest Microsoft Platform SDK installed.

 

If you are developing new for VS 2005, it is highly recommeded that you use the VS 2005 C-Hook wizard as your starting point for development.

[markov]

I can compile my C-hook for X2 now, but it crashes Mastercam when it tries to open a dialog box. I migrated the VS2003 project into VS2005, made the changes mentioned above, changed the include and library path to point to X2 SDK (I created a different installation for X2), added UICtrls.lib to link command line and recompiled. Then I did the same exercise with sample C-hook with modal dialog that VS2003 wizard creates with the same result. Running under debugger produces 4 message boxes about missing DLLs which I am not concerned to much about (c:mcamx2sdkdebugResourceartRes.dll, c:mcamx2sdkdebugResourceEngraveRes.dll, c:mcamx2sdkdebugResourcerast2vecRes.dll, c:mcamx2sdkdebugResourcetxtchainRes.dll), but then it crashes with stack overflow exception after failing several assertions.

 

Any suggestions what I may have done wrong?

 

Marko

[Takashi Sato from Ai Solutions.]

Did you run c:mcamx2sdkdebugmastercam.exe?

 

http://www.emastercam.com/cgi-bin/ultimate...c;f=13;t=000320

[markov]

Yes I did when running under debugger. The non-debug version also crashes when running release C-hook.

[Takashi Sato from Ai Solutions.]

Are you using MCDialog class?

 

and even if you dont call Domodal(),does your chook still crash?

[markov]

Yes, I am using MCDialog - it is the C-hook created by the wizard. And no it does not crash if I do not call doModal.

[Takashi Sato from Ai Solutions.]

OK, I see.

I did the same as you did.

and my chook also crashed.

 

So I deleted this 2 lines, and it works fine.

code:

---

//DDX_Control(pDX, IDOK, m_ok_pb);

//DDX_Control(pDX, IDCANCEL, m_cancel_pb);

---

I'm not using MCDialog class for my chooks, and I did not notice that.

because I wanted MR2 X2 compatible chook..