run_post_exe_dll and overiding ctrldef

[bryan314]

Currently I'm running a single NCI file thru multiple posts with run_post_exe_dll for a custom multipost chook.

 

This worked just dandy in 9 but the way X works by overriding the post values with the Machine Def/Ctrl Def values is causing me problems.

 

Is there a way to tell the post processor to ignore the Machine/Ctrl defs values and only initialize the values from the Post when calling run_post_exe_dll?

 

The only solution I've found is to re-reset the values in psof$ of the post processor. Which basically neuters the users ability tweak setting when posting via the ops manager. Something I don't really want to do.

 

Bryan

[Roger Martin from CNC Software]

quote:

---

Is there a way to tell the post processor to ignore the Machine/Ctrl defs values and only initialize the values from the Post when calling run_post_exe_dll?

---

I believe the answer to that is... No.

[bryan314]

Thanks Roger. I was afraid of that. I've been playing around with posts, chooks, and whatnot all day and I think I have a solution that lets me have the best of both worlds. So the lack of an internal switch isn't too big a deal.

 

As a matter of curiosity? When mp.dll loads and parses the post does it read/set those variables and then supersedes them with the control def values? Or does the dll just set them off the control def and ignores the initial assignment statements in the post altogether?

 

Bryan

[Roger Martin from CNC Software]

When MP.dll loads and parses the post it sets those variables that are declared (initialized) in the PST and then supersedes them with the control def values.

[bryan314]

Thanks Roger. I figured it was something like that.

 

Bryan