Evaluating Text in a Note with NXOpen .NET

[HazelrahBL]

Hello,

This is a question for people familiar with NXOpen.

I'm working with DraftingSheets that have notes on them which reference attributes defined in the part (i.e. "<W@ATTRIBUTE_NAME1>-<W@ATTRIBUTE_NAME2>").

I've been looking through the NXOpen .NET API reference and simply cannot figure out how to evaluate the text in the note to get the actual value displayed on the draft.

I know I can analyze the string and get the attribute names from which I can look up the values, but it seems to me NX should have this built in. They have this for Tabular Notes (Tables) in the form of Tabnot.AskEvaluatedCellText(), so it makes sense that you should be able to do this for normal notes too.

Thank you for any help!

 

[JohnRBaker]

Tables act the way they do because they use a 'spreadsheet' type data record, therefore, by definition, evaluating a 'cell' is what's happening all the time. Granted, it would be nice that 'notes' behaved the same way, but that would require additional code to be written while the 'spreadsheet' like behavior, and thus, the evaluation tools, come for free.

Now if you wish, call GTAC and have them open an Enhancment Request.

Now the good news is that how text is displayed and recorded as 'notes' on a Drawing is getting a reworking in NX 8.0 so it possible that there may be some improvements in this area coming as part of the overall project, and besides, now may be a good time to get those ER's in since there is work already being done in that part of the NX code.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[HazelrahBL]

John,

Thank you for your fast reply!

That is disapointing to hear. Obviously they display the evaluated text on the DraftingSheet so they have the evaluation algorithm built into it somewhere. Just wish that it was on the public side for us to use.

I'm in Japan and we're generally stuck a version behind the current at all times, so for now I'm just going to have to write my own string evaluation algorithm I guess.

Thanks!