Call the components bind() methods to activate them. Also, verify that each adapter meets the contract with the components
Binds the main dialog buttons. For OK/Cancel/remove, the logic calls the appropriate derived function, which calls the appropriate adapter method, then calls complete() to restore the event handling loop to the application
If there is any undo or restore to be done when the dialog clicks OK, that is handled by the adapter. Else it can be a noop.
When a component changes, it notifies the parent dialog. Usually, we just proxy the call to the adapter. The specific dialog can override this method if something in the UI needs to change as a result of the component state (e.g. show or hide another component)
If there is any 'saving' to be done when the dialog clicks OK, that is handled by the adapter. Else it can be a noop.
Used by text editing components that are also event sinks
returns the DOM id of the dialog.
gets the 'modifier' from parent dialog, used by text editors. Most components won't need this.
Gets the static text <string, string> for the current language. this is used by components that have different text labels for different states.
gets the view from the parent
Called before dialog is displayed. components that interface (bind) with the adapter are called 'bound' components. On initialize, update the component with the score value, as told by the adapter.
For score artifacts that can be removed,
Generated using TypeDoc
Load a music XML file