Pros and Cons of QX11EmbeddedContainer....
Pros:
1.Embed third party applications in the container widget allowing integration of QT with third party application.
2.Follows XEmbed protocol which allows embedding the XEmbed widgets to be embedded to the container.
3.Can embed Xembed widget, but the windows ID of the widget needs to be passed on to the container.
Cons:
1. In case of third party applications the windows ID of the application needs to be passed on to the container to embed the application to the container.
2.There is no way container or QT can know the windows ID of the application thereby the application cannot be embedded to the container programmatically.
3.The windows ID of third party applications can be obtained manually by the xwininfo command from the command prompt. But for practiacal purpose this method is of no use for any integrated application containing QT container and third party application.
4. If the above points are true then practically there is of no use for QX11EmbeddedContainer in QT.
Re: Pros and Cons of QX11EmbeddedContainer....
Quote:
Originally Posted by
in_dbasu
2.There is no way container or QT can know the windows ID of the application thereby the application cannot be embedded to the container programmatically.
It works the other way round. You pass your window id to the other application.
Quote:
4. If the above points are true then practically there is of no use for QX11EmbeddedContainer in QT.
MPlayer is an often used application embedded with XEmbed.
Re: Pros and Cons of QX11EmbeddedContainer....
The point remains the same isn'it...whether the application will be embedded on the container depends upon the third party application which the programmer does not have any control over..if the application does not receives the Window ID of the container or if the application does not provides its own window id then the application can not be embedded to the embedded container.
Re: Pros and Cons of QX11EmbeddedContainer....
Quote:
Originally Posted by
in_dbasu
The point remains the same isn'it...
No, not really.
Quote:
whether the application will be embedded on the container depends upon the third party application which the programmer does not have any control over..if the application does not receives the Window ID of the container or if the application does not provides its own window id then the application can not be embedded to the embedded container.
I don't see your point. Nobody said you could use XEmbed with any possible application. Both applications have to support the protocol. One provides a canvas to render to by passing its window id to the other application (usually via a commandline argument) and the other uses the id to embed itself in a given window.
