From 86f63b95c4b97952aa278a7f97a1bfcc2c7b2477 Mon Sep 17 00:00:00 2001 From: Vadim Zeitlin Date: Wed, 30 Jul 2003 15:00:17 +0000 Subject: [PATCH] mention wxWS_BLOCK_EVENTS change git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@22382 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/changes.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/changes.txt b/docs/changes.txt index 5c979a6015..822ef62363 100644 --- a/docs/changes.txt +++ b/docs/changes.txt @@ -68,6 +68,12 @@ All (GUI): generated at all, so you must call event.Skip() in your OnKeyDown() if you want to get OnChar() as well +- the (command) events are not propagated beyond the first top level window + containing them because they now have wxWS_EX_BLOCK_EVENTS style by default, + you need to explicitly unset it if you want to have the old behaviour when + you could process the events from the controls in a dialog in its parent + frame. + - in general, the key events sent for the various non ASCII key combinations have been changed to make them consistent over all supported platforms, please see the wxKeyEvent documentation for details @@ -216,7 +222,6 @@ wxMotif: - fixed "make install" ->>>>>>> 1.212.2.72 2.4.1 -----