Callback Registration for NX Open for Java

The addMenuAction method (on menuBarManager) registers a callback with NX. The name passed must match the string used as the ACTIONS value in the menu file (e.g. "my_app_hello", "my_app_goodbye"). The example (HelloGoodbye.java) registers the entire HelloGoodbye class for both actions in an initializeCallbacks method; since one class handles two behaviors, its actionCallback method determines which button invoked the callback before dispatching to helloCB or goodbyeCB. After compiling, HelloGoodbye.class goes in the startup folder alongside a matching example menu file.

Compilation (Windows)

1. Copy HelloGoodbye.java and HelloGoodbye_Makefile_win to your machine.
2. Start the NX command prompt (Start → Programs, same cluster as the NX shortcut).
3. cd to the folder containing the files.
4. Run: nmake -f Makefile_win

Compilation (non-Windows)

1. Copy HelloGoodbye.java and HelloGoodbye_Makefile to your machine.
2. Run ugmenu, select "UGOPEN-API" → "Non-menu activities" → the shell type.
3. cd to the folder containing the files.
4. Run: make

Source structure (HelloGoodbye.java)

import nxopen.*;
import nxopen.menubar.*;
// HelloGoodbye class demos a custom application with two menu callbacks,
// registering itself as the handler and dispatching in actionCallback()
// to helloCB() or goodbyeCB() based on which button fired the event.

Related Topics

• Programs, Journals, or Callbacks from New Menu Items — Overview
• Introduction to Menu Files
• Executing Programs
• Executing Journals
• Executing Callbacks (Menu Event Handlers)
• Callback Registration for NX Open for C++
• Callback Registration for NX Open for .NET