On Dec 11, 2012, at 1:30 PM, Alberto Mardegan <[email protected]>
 wrote:

> OK. Though I'd prefer to call it Qt::ForeignWindow, to make it obvious 
> that it's not owned by this process (Qt::NativeWindow just seems to tell 
> that the QWindow is associated with a native window, which is always 
> true, AFAIU).

Yes, ForeginWindow is better. The Cocoa use case is slightly different: we are 
wrapping in-process views which Qt owns (in the resource management sense). 
It's still a QWindow with foreign content though.

> 
>> - An basic API for setting the native window*, for example a function 
>> exported by QPlatformNativeInterface.
>> - Nice API in QtMacExtras
> 
> What API would you need?

A type-safe API, plus an implementation of QMacCocoaViewContainer (the widget 
which used to do this in Qt 4).

Morten


_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to