On Mar 27, 2010, at 1:23 AM, Alexander Bokovikov wrote:
On 27.03.2010, at 12:48, Ken Thomases wrote:
I'm not really sure what you're asking for. A modal window being
shown on screen is not something that happens spontaneously _to_
your application, it's something that your application does. So,
whatever you want to do after the window is shown, just do it after
the point in your code where you show it.
I tried to achieve the next effect: some automatic process should be
started on the modal window appearance on screen. A popup panel with
progress indicator appears, etc. My idea was not to initiate such
process from the calling code (where modal window is called from), but
do it asynchronously, as soon as the modal window will appear on the
screen.
Of course, I've solved the problem by calling this process from the
calling code just before [NSApp runModalForWindow:] call. But it is
not pretty correct from the OOP philosophy point of view, at least as
I understand it.
Well, if you're using runModalForWindow: and relying on it to show the
window, it goes away before the method returns, so there is no point
in the code after show and before hide.
But you can always do makeKeyAndOrderFront: explicitly:
[myWindow makeKeyAndOrderFront:self];
// Stuff I need to do
[NSApp runModalForWindow:myWindow].
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
