I have echo Tims comment, we have an update feature now why aren't we seeing small (weekly?) bug fix upgrades? Seems like this would cause fewer regressions. If a weekly patch contains 10 bug fixes and something goes buggy it'd be easier to find the regression than say a SP 4 months from now fixing 200 things. Leave the maintenance releases for what they are for. Feature enhancements not bug fixes. just my 2cents. Bryan

Charles, No problems with that. I do the same with our operation libraries. When you re-save the file make sure the 'save picture' is unchecked (I can't think of the exact text). This will make the file much smaller. Bryan

Fancy name for plugins. Bryan

Not me. Bryan

Paul wrote: quote: There is always the option of moving to the software side of things ... often hire Mastercam programmers that work for their customers... Bryan Vanxxxx, b-r-Y-a-n [email protected] Currently located in Western Michigan. Will consider relocation. (If my boss is reading this, just keeding, just keeding.) Bryan

+1 me Bryan the post count floozy

Post (specific) questions to the forum. There's a lot of talent around here. And people are always ready to help. +1 trial and error +1 cd also sometimes your dealer may have an older book which is easier to flip thru than the cd. trial and error; translation => Bryan

Uncheck the 'use contruction attributes' in the translate dialog box, if it's checked. Bryan

There's a script SaveBackup-Mick.zip on the ftp server under vb_scripts directory that will do that. Do a search on the forum there are several scripts floating around. I believe Rekd did one that backed up to RAR files and James did one to Zip files. Bryan

I've seen something similar with Microsoft Office97 and a program it installs called Fastfind. The Fastfind program will map network drives under different letters for drives already mapped. Bryan

I though maintenance was for new features and bug fixes were going to be released seperate for us poor saps that don't have maintenance? I can understand if the fixes are for maintenance items but if they're not.... Bryan

but you still get X for free when it comes out? right? [ducks and hides] Bryan

try combine views too. bryan

bryan

Paul unclick save thumbnail image with geometry when you resave the file. the image MC saves with file takes up a lot of room. Bryan

backup defaults.df9 rename defaults.df9 to defaults.mc9 open defaults.mc9 in mastercam make changes. one by one or use edit-common params save defaults.mc9 rename back to defaults.df9 mc9, op9, df9 etc are all the same. Just mc9 files. Bryan

Not for forward pointers but converting bad files I use the tape dispenser. (I'ts weighted.) Bryan

Oops, forgot to hide the console window. Bryan code: #include <stdio.h> #pragma comment( linker, "/subsystem:"windows" /entry:"mainCRTStartup"" ) int main(int argc, char *argv[]) { return 0; }

Hey, I might have the source code to that editor. Bryan code: #include <stdio.h> int main(int argc, char *argv[]) { return 0; }

A while back I ran into editor weirdness if the variable bug1 in the post was set to 2. It'd still come up even if I say no to edit nc in the post dialog. bug1 : 2 # 0=No display, 1=Generic list box, 2=Editor This may or maynot be related to your problem. Bryan

1. Setting the blank bit is probably equivalent to screen-blank, probably not good. I don't remember any function for directly manipulating screen-hide equivalent but you can probably manipulate the display_list structure in m_vars.h. I can email you some code that might get you started if you're interested. 2. I use a combination of postOps and run_post_exe_dll to bypass those annoying boxes for a custom multipost chook. postOps to generate the nci file. run_post_exe_dll to run that file through multiple post processors. I found if you want to use postOps multiple times on one op it regenerates the nci code each and every time. doh. A real pain if you're posting a crap load of surface operations. The only gotcha I had with postOps was to backup the current post_settings variable and then restore them when I was done or postOps overwrote the current users posting settings for that session. Bryan

Here The best responses I've got from other members and MC employees is just asking specific questions like you did. Bryan

Thanks. mprintf is just for debugging, enter your error handling of choice. +1 post count Bryan

Based on Gismo's comments, this works as a 'safe' exit for me. This allows MC to call m_close when m_open is used. Since you seem to be using MFC/C++ it'll probably need be changed slightly. Bryan code: void your_function(void) { HWND mc_handle = (HWND)dbm_get_mainwnd_id(); if(mc_handle != NULL) { /* remove 'MC9 file has changed. Save it?' dialog box. changes since last file save are lost */ set_db_unchanged(); /* send exit command */ PostMessage( mc_handle, WM_CLOSE, 0,0); /* answer yes to 'Do you really want to exit Mastercam' dialog box */ #ifndef VK_Y #define VK_Y 0x59 /* not always defined */ #endif keybd_event( VK_Y, 0, 0, 0 ); return; } /* debug */ cleartextall(); mprintf("can't find MC EXE handle.n"); wait_for_space(); cleartextall(); /* debug */ }

...but would it be too much to ask for the person who posted that document to the FTP site to also post the missing function? Sometimes it's like trying to get blood from a stone to get MC to provide example for the SDK. If you want a 'dirty' way to close mastercam call the C exit() function. code: exit(EXIT_SUCCESS); This is a rather abrupt way to close mastecam and may cause problems. For example: if there is a chook using m_open instead if m_main as the chook entry point, so the chook can run continuously in the background, Mastercam doesn't have the chance to call m_close for the chook and allow for any clean up. Like releasing allocated memory and causing a memory leak. Bryan