On 2008-04-29 09:11:31 +0200, Trenton Schulz <[EMAIL PROTECTED]> said:
On 2008-04-28 20:20:25 +0200, "Yan Shapochnik" <[EMAIL PROTECTED]> said:
[snip]
Do you think implementing something like this is possible?
What you said was essentially correct. We can work around the qtPrivate
issue by making it a category. The problem is that NSApplication (and
Cocoa in general) has the idea of one delegate and no "bubbling" up of
events. It's one place where Carbon events really, really shines. It is
possible to work around this, but only in an informal way that others
have to agree to (basically publish our QCocoaApplication). The problem
is that, unless the developers control the application (a.k.a.
application developers and not plugin developers), they might not have
the abliity to even agree. I'm still not a Objective-C guru, so if
there for some reason is someone here that has an idea I'll certainly
listen.
The only other way I can think about it is that we essentially say,
"these things won't work if Qt can't control NSApplication." What that
list is, I can't say at the moment.
The best I can tell you at the moment is that we are aware of this and
that people do use Qt in plugins on Mac OS X and that they should be
able to do that in Cocoa. What is the current implementation to will
achieve that? I don't know at the moment, but we want to solve it.
Probably not the best answer ever, but hopefully it helps answer your question,
I've made some changes to this, so it at least shouldn't be crashing
anymore. It doesn't solve the delegate problem yet. I have some ideas
for it, but I need to thnik about how plausible they are.
I will at least warn about this situation, so it's a better than it was.
You'll have to keep your eye on this when we get around to pushing
another alpha out,
Thanks,
-- Trenton
To unsubscribe - send "unsubscribe" in the subject to [EMAIL PROTECTED]
