cancel
Showing results for 
Search instead for 
Did you mean: 

Putting Info at start of program.

Creator
Creator

I'm needing to put some info at the start of each file i postprocess.

ie.

Drawing name and Rev

Authority model name and rev

Parts lists and Rev

 

what is the easiest way to implement to where each time i repost, im not having to edit it in manually.

Im decent at post editing, and can pull in info i need, as ive done with file names, dates, tool data.

 

but where would i put this type of info in, to be pulled from?

8 REPLIES

Re: Putting Info at start of program.

Esteemed Contributor
Esteemed Contributor

Easiest would be to use part attributes, if they are available.

 

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX12.0

How to Get the Most from Your Signature in the Community

Re: Putting Info at start of program.

Creator
Creator

I don't believe they are. We do not have teamcenter. Unless i'm mistaken and those are available with what we have licenses for, where would i go to check?

Re: Putting Info at start of program.

Esteemed Contributor
Esteemed Contributor

Part attributes are ALWAYS available.

Teamcenter just automates assigning a few specific ones.

 

If you don't like the attribute interface, or whatever, you can always code a small journal with a Winforms or Block styler interface - at least then the attributes will always have the correct names.

You might be able to menuscript this as a "post" action on the File -> New dialog, so users don't forget ;-).

 

Note you can also pre-create attributes in a catalog, so all users need to do is assign values.

 

Ken

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled


Re: Putting Info at start of program.


MtnJunkie78 wrote:

I'm needing to put some info at the start of each file i postprocess.

ie.

Drawing name and Rev

Authority model name and rev

Parts lists and Rev

 

what is the easiest way to implement to where each time i repost, im not having to edit it in manually.

Im decent at post editing, and can pull in info i need, as ive done with file names, dates, tool data.

 

but where would i put this type of info in, to be pulled from?


Where is the information stored? i.e. where will you get it FROM?

Mark Rief
Retired Siemens

Re: Putting Info at start of program.

Creator
Creator

Thank you for the comments.

 

I think the Part attributes is what ill be trying.

We dont have special License's for NX customization, so i'm guessing that negates the Block UI part of it?

 

If so i'll probably just try a journal that at least sets the Attb's as blank, so name's are always right?

 

Reading into how to code that journal now. Smiley Happy

Re: Putting Info at start of program.

Esteemed Contributor
Esteemed Contributor

I think the license for the Block Styler is just for the GUI to create the DLX file.

I *think* (someone please correct me if I'm wrong) there are some API calls to create dialogs on-the-fly.

 

In any case, you could create a WinForms interface (assuming you're on MS Windows).

 

Also, you can search the docs for "attribute template".  This is an XML file you can define/edit to "pre-create" attributes you want (the user then just has to find the attribute they want and give it a value).  If the journal doesn't create the attribute, I would suggest trying to set these up, to reduce typos by users.

 

Have fun!

 

 

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled


Re: Putting Info at start of program.

Phenom
Phenom
I think the 'on the fly' dialog creation is only available in SNAP.
Graham Inchley Snr R&D Engineer (Systems Development), Sandvik Coromant
Lenovo ThinkPad W540, Win7, 16GB. Developing in: Java | C | C# | KF
Production: NX8.5.3.3 MP11 64bit Testing: NX9.0.2.5

Re: Putting Info at start of program.

Esteemed Contributor
Esteemed Contributor

Bummer, unless they are part of MiniSNAP.

 

Note there are other UI routines that you can use (uc16** and UF_UI_* are the legacy calls, I think there's some newer ones as well) but you may end up having to post several dialogs to get all the info, so it would probably be better to use Winforms.

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled