Jbrunelle
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by Jbrunelle
-
-
Thanks for the response. I hadn't seen any examples labelled as "ToolNetApi" so far, but i'm looking into a few now.
The few I've seen so far look like they're specifically targeting the *.DB files.
Since I'm trying to get a list of tools used on a given job (within a specific .mcam file), I'm not sure how this api helps / I can't find anything to help.
I essentially already have the info I need and my program is working properly (mostly):
This is effectively all the info I need from a given file. The problem is this error message (and others like it) that requires manual input:
Is there any way to bypass this error/warning message? Or even temporarily disable warnings from within Mastercam or something?
Otherwise, if there is something within ToolNet that i'm missing, so more guidance as to where to look would be appreciated.
Thanks!
-
Hello,
I'm attempting to read a list of tools out of a bunch of mastercam files using Nethook/C#
The base structure is this (which works as expected):string filepath = "C:\\TEST\\TEST.mcam"; FileManager.Open(false, filepath); Tool[] mcamToolList = SearchManager.GetTools();
Unfortunately, some of the files have errors/warnings when opening, and mcam presents a dialog saying "There were one or more errors...".
I can manually click "OK" and continue on, but with multiple files, I would prefer to avoid manual interaction.
Is it possible to suppress these error messages?
Otherwise, on a related note - Is there an alternative to FileManager.Open()?
I would like to "activate" the database so SearchManager can interact with it - is there a way to "get" a database without using FileManager.Open?
(i.e - I would like to read the file contents into a DB object without actually Opening the file)
Thanks!
Errors on Open (NetHook, C#)
in Mastercam C-Hook, NET-Hook and VBScript Development
Posted
This seems like something that may work for me, I'll look into it a bit on my end.
Also... Thanks for the link to that other thread! Reading through that should keep me busy for a while.