Block Styler Automation (NX Open Programmer's Guide)

The Block Styler is an interactive tool for designing NX dialogs. It supersedes the older "UI Styler". Key quote:

The Block Styler enhances the capabilities of the UI Styler by using the same set of reusable blocks currently used by internal NX applications. Using Blocks as the basic dialog building units ensures that NX has consistent behavior across all applications. By using the Block Styler your custom applications will share the same user interactions as used throughout NX.

Confirms (again, independently of the Tree List doc) that Block Styler blocks are literally the same widget classes NX's own built-in dialogs/applications use — not a look-alike.

Workflow: design a dialog in the Block Styler UI → it generates a .dlx file (runtime dialog definition, read by NX) + template source code (the callback scaffolding you customize) in your chosen NX Open language.

Searched for and NOT found on this page

Searched this page's full text for Resource, dock, embed, ResourceBar, Explorer — none appear. This page describes only the design/codegen workflow for BlockStyler dialogs (shown via Dialog.Show() as modal/modeless windows). It gives no documented mechanism for hosting/reparenting a BlockStyler-generated control (e.g. the Tree List from blockstyler-tree-list.md) inside a ResourceBarManager custom tab's docking window the way our Qt widget is embedded in ArchitectureTab.cpp.

Conclusion for spine-panel-kit

The two officially documented, independent mechanisms are:

1. ResourceBarManager (Create/GetWindowHandle/etc.) — hosts any Win32 HWND in a resource-bar tab. This is what we use today (Qt widget inside it).
2. Block Styler Tree/Node blocks — build a dialog control that looks and behaves exactly like NX's native navigators, but is documented only as being shown via the Block Styler dialog runtime (.dlx + generated code), not as something you reparent into an arbitrary host window.

No doc page found (yet) bridges the two. Whether a BlockStyler Tree can be extracted from its owning dialog and reparented into our ResourceBarManager container HWND is an open engineering question, not a documented pattern — would require direct experimentation (e.g., inspecting whether NXOpen.BlockStyler.BlockStylerDialog exposes a raw window handle) rather than further doc search.