Displaying host windows for third-party applications

You can create custom Resource bar tabs to display third-party applications in NX. Your application looks like it is a part of NX instead of opening it in a separate window.

In the reference figure, the title of the custom window is "My Tab 1". Below the title are examples of options that a third-party application might include.

Use the following NX Open APIs to define and control the tab and window (all on the ResourceBarManager class):

API	Purpose
Create	Creates a tab, which is added to the resource bar when you set the visibility.
RegisterActivationCallback	Activates and displays the custom window when you click the tab.
ActivateTab	Activates and displays the custom window immediately; you do not need to click the tab.
GetWindowHandle	Creates an NX docking window, which is used as the parent to host your custom window.
SetTabVisibility	Controls the visibility of the tab in the Resource bar area. If you hide a tab using this API, NX does not display the hidden tab in the list of available tabs in the Resource bar area.
Destroy	Removes your custom window and tab from NX.

Note: The application that is being hosted controls the behavior inside the host window.

Where to find it: these APIs are in the ResourceBarManager class — see the NX Open Programmer's Guide for full signatures.

Relevance to spine-panel-kit / ArchitectureTab.cpp

This is the exact, official pattern our ArchitectureTab.cpp already implements: Create("Architecture", "styler_tree") → RegisterActivationCallback → GetWindowHandle (container HWND) → our own Qt widget embedded inside it → ufusr_cleanup() calls Destroy. Confirms the approach is correct per Siemens' own docs. Does not address native table/tree styling — this page is scoped to window hosting mechanics only, not visual appearance. See open question: how NX's own navigators achieve their look (tracked as a gap — NX's internal trees are not Qt widgets in a shared QApplication, per our own process-memory investigation).