From e2da259b5733a36f8b4f934869f02ea7ee5163db Mon Sep 17 00:00:00 2001 From: Caolán McNamara Date: Tue, 1 Sep 2020 14:44:25 +0100 Subject: SetCallHandlersOnInputDisabled is newly unused MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Change-Id: I4225ce786b83f44178a477ac034d8f8f5198159e Reviewed-on: https://gerrit.libreoffice.org/c/core/+/101852 Tested-by: Caolán McNamara Reviewed-by: Caolán McNamara --- include/vcl/window.hxx | 17 ----------------- 1 file changed, 17 deletions(-) (limited to 'include/vcl/window.hxx') diff --git a/include/vcl/window.hxx b/include/vcl/window.hxx index 24b74328dc63..458b225f26d8 100644 --- a/include/vcl/window.hxx +++ b/include/vcl/window.hxx @@ -983,23 +983,6 @@ public: */ void AlwaysDisableInput( bool bAlways, bool bChild = true ); - /** usually event handlers (see AddEventListener and AddChildEventListener) - are not called on disabled, modal or input disabled windows. There are however rare cases - in which one wants a Window or rather one of its Control subclasses to - not evaluate events but still react to those events externally. In these - rare cases call SetCallHandlersOnInputDisabled( true ) to have your handler - called anyway. - - Currently only mouse events get this special treatment. - - Use this sparingly, chances are if you want to use it you're working around - the real problem. - - @param bCall - Enable/Disable calling event handlers for this disabled, modal or input disabled window. - This call is implicitly done recursively for possible child windows. - */ - void SetCallHandlersOnInputDisabled( bool bCall ); /** get state of SetCallHandlersOnInputDisabled @returns whether handlers are called regardless of input enabled state -- cgit