Well I was going to have a cool new tool finished today for filling in drawing formats but I ran into a hole in the NXOpen API for python.

My presentation got approved for public release, so my #PLMConx talk is really happening!
"Logical Note Selection Tool in NXOpen & Python 3"

My #PLMConx presentation is soon! Room 144 at 3:45. Python 3, NXOpen, Logical Note Builder. Storytime, Book Learning, Adventure Preparation.

Got another tool working in NXOpen #Python, co-worker asked how long it took me.

A: many hours spinning wheels + ~20 minutes of brilliance.

I wonder what it's like to develop code with a well-documented API? #NXOpen #Python #trialanderror

NX (@Siemens CAD software) has an application called "Block UI Styler" which lets you build dialog boxes to go with NXOpen-scripted tools.

I spent today figuring out the architecture of my next NXOpen tool by building & modifying the #UI in Block UI Styler.
Python code tomorrow.

Anyone else I know online a member of "Siemens PLM Community" forums? I found & friended @burhop & @dorasmith already today. #NX #NXOpen

I spent most of today on resolving this #NXOpen #Python #API #crash:
https://community.plm.automation.siemens.com/t5/NX-Programming-Customization-Forum/PMI-annotations-I-create-in-NXOpen-crash-NX-if-Settings-are/m-p/433358

TIL because I develop NXOpen code now, our MCAD tools group has elevated their opinion of me from "POWER user" to "COOL user" which means I can test their work-in-progress systems much earlier.

Nearly done with my part of a Digital Thread project to connect OpticStudio (ZEMAX), NX, & ANSYS to predict accurate optical effects of transient vibration! So far I'm writing in ZPL & NXOpen Python 3.

Twenty hours of coding later, it isn't going well. NXOpen tags giving me problems again...

Kind of excited because I've gotten permission to spend some time fixing a Python-coded NXOpen tool I wrote that has been neglected for a year. The bugs finally got bad enough...

This is after wasting hours this morning trying to get #NXOpen to tell me which button on the ribbon was *just pressed* to launch the #Python journal. There's a thing called MenuButtonEvent related to the MenuButtonManager, but I could not figure out how to refer to it correctly.

TIL that #NXOpen #Python really doesn't like using argparse but using sys.argv works fine instead. Now I can use one .py file for both a "Regular" & an "Express" version of a tool by passing different Journal Arguments from different ribbon menu icons.

My problem/program with the linear algebra coordinate rotations & the digital thread (& the NXOpen Python3 API missing a critical function) might almost be resolved?

I'm already fairly sure that once I find it, the solution is going to be super basic & obvious in hindsight.

I think I got my program working today? I had to stop trusting the NXOpen API to do what its documentation said it did. Checked everything every step of the way, adapted accordingly.