From 08fa68db86928852e7b025b76059fcceceedf325 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Caol=C3=A1n=20McNamara?= Date: Thu, 12 Dec 2019 16:00:40 +0000 Subject: [PATCH] tdf#127919 link Assign Component dialog to 'Creating A Dialog Handler' MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: Ie0f7b0e45ebf0e39d67abc36640cdffd22e08e29 Reviewed-on: https://gerrit.libreoffice.org/85064 Tested-by: Jenkins Reviewed-by: Caolán McNamara Tested-by: Caolán McNamara --- source/text/sbasic/python/python_handler.xhp | 1 + 1 file changed, 1 insertion(+) diff --git a/source/text/sbasic/python/python_handler.xhp b/source/text/sbasic/python/python_handler.xhp index 1f9e9ce354..87887105e3 100644 --- a/source/text/sbasic/python/python_handler.xhp +++ b/source/text/sbasic/python/python_handler.xhp @@ -23,6 +23,7 @@ API;DialogProvider2 API;XDialogEventHandler +

Creating a Dialog Handler

Next to assigning macros to events or creating event listeners, 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 vnd.sun.star.UNO:<method_name> 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. The advantages of this approach are: