It depends on what you want with the template.
If it's meant for local use on that machine - go ahead and select "update the pax file" (so you don't need to edit it manually).
If it's for distribution to other machines/user roles, there's probably no point in updating the pax file of your...
Given that the pax file is a directory of templates available in the File-New dialog, not updating it will result in your new template not showing up on that dialog.
When your NXOpen programs grow out of the simple Journal files, Siemens wants you to have the Authoring license to be able to sign your dlls, so that other people can use them.
For .net applications, you need to add the NXOpen Signing Resource thingy (UGOPEN\NXSigningResource.res) to your...
The red dot tells you where the problem is, most likely some sort of distance tolerance issue. You can sometimes "fix" it by twiddling the tolerance value, but a lot of the time it's some sort of geometry problem that you might want to address before this thing is created IRL.
You can create a dummy assembly with some basic blocks to show us here, and also verify that this behaviour is reproducible with any model.
Otherwise we're reduced to making guesses.
Are there any other objects in the assembly, that are overlapping with the hidden assembly components, like...
You can record NX Journals while performing simple tasks to learn how NXOpen does stuff from these.
Recorded Journals tend to get excessively verbose when you record more than a couple simple actions (running the risk of drawing you into cargo-cult programming), but this should be bearable for...
Yeah, they added the whole symbolic thread stuff into the "modern" NXOpen, while simultaneously obsoleting the old C function wrappers back in 1926 or so. This function will now only work for the old pre-1926 holes.
You'll have to re-record/rewrite the Journal using the "modern" functions...
Having used keyboard and mouse for the majority of my waking life over the last 35 years, and never having any issues, I'm going to guess it largely depends on workplace and tool ergonomics.
Holding the mouse at weird angles, having the table edge cut into your forearms, or forearms hanging...
patternFeatureBuilder1.FeatureList should have it.
Depending on the designer's "creativity," the list may have more than one feature, even more than one hole package, so you'll need to look for the one you need in there.
You can probably avoid the error by replacing that one line with the following:
If myBody.IsOccurrence() then
Dim bodyInPart = CType((myBody.Prototype), NXOpen.Body)
bodyInPart.OwningPart.LoadFeatureDataForSelection()
Tree_Obj_feature=bodyInPart.getfeatures(0)
else...
I think you can create a custom user role with the modified ribbons for that and roll it out to target users. NX doesn't like you modifying its core menus and will want to overwrite them with each update if you do.
We maintain our own menu and ribbon, and "patch it in" via the custom_dirs.dat...
You can do it from within the NX UI (right click-customize), why would you want to do it the hard way?
But yes, Ribbons are essentially repurposed toolbars, so you can edit them in the same manner.
You can usually toggle this functionality in the manufacturer-supplied app or in the laptop BIOS, so that you won't have to press fn every time you need to use an function key.
No, you are correct. If you open the "ug_main.men" as lklo suggested, you can find the "UG_TOOLBOX" there as a button and as a menu, and it has a "LABEL &Tools" element, solving your confusion.
I don't know if there's an official naming list or anything, but you can glean that from working menu...
