tdf#127919 link Assign Component dialog to 'Creating A Dialog Handler'

Change-Id: Ie0f7b0e45ebf0e39d67abc36640cdffd22e08e29
Reviewed-on: https://gerrit.libreoffice.org/85064
Tested-by: Jenkins
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
This commit is contained in:
Caolán McNamara
2019-12-12 16:00:40 +00:00
parent 96c9eaf346
commit 08fa68db86

View File

@ -23,6 +23,7 @@
<bookmark_value>API;DialogProvider2</bookmark_value>
<bookmark_value>API;XDialogEventHandler</bookmark_value>
</bookmark>
<bookmark xml-lang="en-US" branch="hid/cui/ui/assigncomponentdialog/AssignComponent" id="bm_id66701251" localize="false"/>
<h1 id="N0665"><variable id="pythonhandler_h1"><link href="text/sbasic/python/python_handler.xhp" name="Creating a Dialog Handler">Creating a Dialog Handler</link></variable></h1>
<paragraph role="paragraph" id="N0666">Next to <link href="text/sbasic/shared/01040000.xhp" name ="Assigning macros to events">assigning macros to events</link> or <link href="text/sbasic/basic/python/python_listener" name ="creating event listeners">creating event listeners</link>, one can use dialog handlers, whose principle is to define UNO keywords, or methods, that are mapped to events to watch for. The event handler is responsible for executing methods using the <literal>vnd.sun.star.UNO:&lt;method_name&gt;</literal> protocol. Unlike listeners that require to define all supported methods, even if unused, dialog handlers require only two methods on top of intended control hook scripts.</paragraph>
<paragraph role="paragraph" id="N0667">The advantages of this approach are:</paragraph>