Messages

11

Mach SDK plugin questions and answers. / Macro trigger in C++

« on: May 12, 2015, 03:36:25 PM »

I always seem to come up with the fun ones:

I am having an issue where I am triggering a macro to run via the MachRemote application using scripter.DoOEMButton(301) call.  I have set 301 to the appropriate macro and the vbscript will run as it should and does what I need when I trigger it in the vbscript editor.  However, when I trigger it using the scripter.DoOEMButton, it will load the file but will display the "Path Generating" Dialog box and not go any further.  I can hit cancel on the box and then continue by stopping and starting the macro in Mach 3, but that kind of defeats the whole point of what I want to accomplish.  Any suggestions on how to get Mach 3 to move past this "Path Generating" dialog box automatically?

12

Mach SDK plugin questions and answers. / Re: External LoadFile command

« on: April 30, 2015, 02:29:19 PM »

I found out that I have to be in the Open File dialog box in order for the LoadFile and LoadRun commands to execute properly.  Anyone know of a way in which I am able to do this without opening this dialog box?  Or how to close it in proper sequence if its necessary to have it open while loading a GCode file?

13

Mach SDK plugin questions and answers. / External LoadFile command

« on: April 29, 2015, 12:29:29 PM »

Hi everyone!

I'm currently trying to build an external C++ program that utilizes the scripting function in Mach 3 based off the MachRemote example on the main site.  I have added a "Load File" button to the screen, sourced it correctly, and am able to run other scripting commands on it like scripter.DoButton(21) and scripter.DoOEMButton(169) so I know the button is sourced and functions correctly.

It is not allowing me to use the LoadFile or LoadRun command.

Here's the section of code that I have:

Code: [Select]

void CMachRemoteDlg::OnBnClickedLoadFile()
{
if (scripter == NULL) return;
scripter.LoadFile("c:\Rosetta.tap");
}
Any suggestions as to why this would not work?