Hi all,
As the use of multiple-inheritance UNO interfaces increases, people
start to stumble over one specific problem: Assume there are two
interfaces X1 and X2, each with a method named foo. Then, you cannot define
interface X3 {
interface X1;
interface X2;
};
as UNO does
Hi Stephan
One case where this problem occurs in practice is with
com.sun.star.lang.XComponent and
com.sun.star.document.XEventBroadcaster. I just learned that Andreas
Schlüns is probably going to add a new
com.sun.star.document.XDocumentEventBroadcaster (or similar) that will
have the
Hi Darragh,
I am slightly disturbed by this, 2 interfaces with the same function names.
Has any consideration being given to language-bindings that do not use
the query-interface mechanism ? I.e pyuno where all interfaces for a
service are returned ? How would pyuno or language_bindings that
Darragh Sherwin wrote:
Hi Stephan
One case where this problem occurs in practice is with
com.sun.star.lang.XComponent and
com.sun.star.document.XEventBroadcaster. I just learned that Andreas
Schlüns is probably going to add a new
com.sun.star.document.XDocumentEventBroadcaster (or similar)
I have no idea how pyuno does it. But note that this problem was
there from the beginning, and has nothing to do with the addition of
multiple-inheritance interfaces. There are, for example, already
cases where one UNO object implements both XComponent and
XEventBroadcaster, and I have
Hi,
I have no idea how pyuno does it. But note that this problem was
there from the beginning, and has nothing to do with the addition of
multiple-inheritance interfaces. There are, for example, already
cases where one UNO object implements both XComponent and
XEventBroadcaster, and I have
