Showing results for 
Search instead for 
Did you mean: 

Betreff: Persistent Object Identifier

Siemens Legend Siemens Legend
Siemens Legend

@MPogue wrote:

Boy, if you didn't know this stuff, I don't know how you'd know this stuff.


This is called interoperability and explained in the documention, see

Interoperation between the Common API and Open C


To get a better understanding of the history and the relation between Open C and NXOpen UF Wrapper, see also

The NXOpen Programmer's Guide is really a good entry and answers many of the typcial questions Smiley Happy

Betreff: Persistent Object Identifier

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

At one point you could take a training course in API from Siemens (I think actually run by DAA, at least at one point).

Not sure if it is still in the catalog.

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

Betreff: Persistent Object Identifier

While courses are nice, I think PLM fixing the underlying problem - bad documentation - would be much better.


While there is an API reference, most functions (mainly looking at Python here, but I think the same is true for all languages) have zero explanation. Especially discovering functionality is extremely hard this way.


e.g. If you don't know handles exist, there are zero cross references from other functions. Like a "see also" in the documentation for Object.Tag.


A while back I proposed having a public wiki for the API reference, so that users can help themselves, but there wasn't much resonnance.


Maybe we all should make a weeky ritual of escalating this to management until they get some priority to do this. I mean, this is not cheap software we're talking about here, and it wouldn't even be that much work. One can dream...


Nikolas Losse | Developer | Siemens PG PR R&D TEC
NX12 | CentOS7 | Python