From 473138bc672123fa3a965f1320e1b08884da620e Mon Sep 17 00:00:00 2001 From: arobert Date: Mon, 28 Feb 2005 04:18:06 +0000 Subject: [PATCH] clarify gsdoc explaining why Apple docs not followed git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/gui/trunk@20808 72102866-910b-0410-8b05-ffd578937521 --- ChangeLog | 7 +++++++ Source/NSApplication.m | 8 ++++++-- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 7c07ed6a8..63ab419f4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,10 @@ +2005-02-27 Adrian Robert + + * Source/NSApplication.m (-runModalForWindow:) Clarify gsdoc + explaining why we don't follow Apple docs here. (Corrects gsdoc + from change on 2005-01-26, which itself documented a code change on + 2005-01-18.) + 2005-02-26 18:04 Alexander Malmberg * Headers/Additions/GNUstepGUI/GSServicesManager.h: Include the diff --git a/Source/NSApplication.m b/Source/NSApplication.m index 32d896fd0..01fe1ed14 100644 --- a/Source/NSApplication.m +++ b/Source/NSApplication.m @@ -1369,8 +1369,12 @@ immediately.

Although Apple's docs state that, before processing the events, it makes the session window key and orders the window front, this method does not attempt - to do this (due to excessive overhead). Therefore you should do it yourself - beforehand, if needed. + to do this, because: 1) we don't want to interfere with use of other apps + during modal session for this app; 2) occasionally other windows are active + and should be usable during modal sessions (e.g., a popup dialog from a modal + window); 3) most of the time -beginModalSessionForWindow: will have been + called in advance. If the latter is not the case, you may need to order the + window front yourself in advance.

See Also: -runModalForWindow: