chook file name setting

[Girus]

Hi,

 

Does anyone know how to set the post (nc) file name programtically.

 

I don't want to post the nc file yet, just set the file name ahead of time so that when I manually press the post button I get the filename that I set by default, instead of the T.NC I normally get.

 

TIA

 

Girus

[cadist]

In your post file add the line sextnc then space and the extension.

eg.

sextnc h

to get h as the default extension for your nc files.

[Bullines]

Check out the nc_filename variable in m_ncvars.h.

[Girus]

Bullines,

 

I found the nc_filename but how do you set it?

 

Girus

[Bullines]

The only time I need the nc_filename is when I post programatically with the run_post_exe_dll() and even then I path out my own NC file anyway.

 

Since it's a character pointer, you probably can modify it directly, though it seems weird in the grand scheme of things.

[Girus]

Yes. This is weird. Maybe there is another way to set it?

 

How about if the MC people step in and help here. please!

 

I need to programtically set the file name and path. My chook program is generation the all of the drawing lines and I also must have a filename that corresponds with what was generated. Hand inserting it at post time is to much time consumming.

 

Girus

[Bullines]

Will you programatically post too? If so, you have more control.

[Girus]

I will programatically post at some point in time, right now I am doing manual operations (some) and some are programatically, but when I get the whole thing done in chook then I will post too. I am learning to crawl then walk and I hope some day Run!.

[Bullines]

Because the run_post_exe_dll() function, which does the actual posting, allows you to specifiy a destination NC file.

[bryan314]

Don't know if this will help but I've had some good luck with the postOps() function in combination with the run_post_exe_dll() function to create a custimized multipost chook.

 

postOps in M_NC.H

post_dlg_settings/post_settings in M_NCVARS.H

 

A very simplified outline of what it does is:

1) Use postOps/post_settings to get some limited user interaction (if needed). We've got the chook tweaked enough that this is now turned off by default.

2) Use postOps/post_settings to generate the text .nci file.

3. Run the heck out of run_post_exe_dll() using the nci file against various postprocessors.

 

Bryan

[Girus]

Thanks to Bullines and Bryan for your help on this.

 

After much aggrivation I have finally achived what I was looking for. I am going to post it here for anyone who may need to do the same.

 

code:

---

//	SetDestinationFilename

// ======================

// Changes the destination NC file name.

// an operation must exist in order for this to be

// successful.

// I - szFileName : the new complete path and filename.

// must be valid.

// Returns: true for success, false for fail.

static boolean SetDestinationFilename( char *szFileName ){

 

boolean succf;

operation op;

db_ptr_type d_ptr;

 

 

// clear the operation.

memset( &op,0,sizeof(operation));

 

// get the first operation.

operation_manager (&op,OPMGR_GET_FIRST_LIST,&d_ptr,&succf);

 

if (succf){

// copy the filename

strcpy (op.cmn.nci_name, szFileName);

// change it!

operation_manager (&op,OPMGR_REWRITE,&d_ptr,&succf);

if(succf){

// regenerate the operations.

operation_manager (&op,OPMGR_NCI_REGEN,&d_ptr,&succf);

} else

return false;

}else

return false;

 

// return true! success!

return true;

}

---

Enjoy!

 

Girus