Some dialogs have a tab bar and display different aspects of the dialog model in different views.
Problem
Currently, you can define commands and dialog openers as buttons only on these views within the tab bar, but not on the dialog itself.
There are commands that relate to the dialog model and for which it doesn’t matter which aspect (tab) is currently displayed.
Either you choose a view in which to place these commands and accept that some users may not find it intuitive, or you have to offer the commands redundantly across all tabs, which leads to many redundant buttons.
Request
It would be helpful to be able to define such commands directly within the dialog and offer them as a parent function—either as a button or as a menu item within the dialog.
Test
In TL-Demo, go to the "Technical Demo -> Components -> Dialogs" view. Open the dialog in the upper-right corner and click the "Message" button in the dialog.
Expected Result: The message “The ‘Message Button’ of the dialog was clicked!” appears at the very top.