Hi,
thank you very much for your answer, Rob.
> I am successfully using modal Cocoa windows in a plugin inside a
Carbon application.
This statement and your code gave me the final hint that it must work
- and that the problem must be found somewhere else.
Using your code nothing changed at all. In fact it would surprise me
if using a loop with a session would be different to calling
runModalWithWindow (concerning my problem I mean).
So I again looked at the documentation - and here we are: do not send
makeKeyAndOrderFront: to aWindow.
But I called makeKeyAndOrderFront and you too.
I removed the makeKeyAndOrderFront call in my old code - and
everything works correct.
Everthing?
No - there is still one minor problem: if I hide the carbon
application and activate it again then my modal window is updated.
But not the current modal dialog of the carbon application (which
calls my modal dialog via user action).
Yes - I know. It is not good practice to show two modal dialogs. But
this is the way the carbon application is doing it. And I can not
change this.
Any ideas how I can "send" a update to the carbon application?
The problem here is that the NSApplication will receive the event -
and will not update the carbon modal dialog.
Cheers
Martin Brodhage
_______________________________________________
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 [EMAIL PROTECTED]
