Block Styler Memory and Callbacks

Before generating template code you have the option to select the set of callback methods that you want to include in your application (see "Code Generation" in the Block Styler User Guide). A callback method is a method that is designed to handle specific types of dialog events. When the dialog is created at runtime the callback methods are registered with NX. While processing user interactions, NX then knows to call your custom methods for the dialog. By adding code to the callback methods, you can implement the dialog behaviors which are required by your application.

This section defines the set of available callback methods and what events are used to invoke each method. Note that all dialogs must provide an Apply and Initialize method. All other callback methods are optional.

Your callback methods will access the current dialog values and may update the dialog values. Block Styler dialogs also have an internal memory. It is important to understand how dialog memory interacts with dialog values across the callback lifecycle — see the sub-topics below.

Sub-topics in this section

• Standard Navigator Buttons — the standard Ok / Apply / Cancel / Back / Next buttons in a Block dialog's rail, and which callback each is tied to.
• Dialog Memory — how a Block Styler dialog persists (remembers) its previous values between invocations, and how that memory interacts with dialog values set by callbacks.
• Dialog Values — how to read and write the current values held by dialog blocks from within a callback.
• Callbacks — the full list of callback methods: Filter, Update, Ok, Apply, Cancel, DialogShown, Initialize. See blockstyler-callback-methods.md for the complete reference.
• Dialog Value Example — a worked example showing dialog values being read/written in a callback.

See the companion file blockstyler-callback-methods.md for the full per-callback reference (this is the most detailed and load-bearing sub-page).