Stephan Bergmann wrote:
UNO structs are not involved in the above. UNO interface attributes
were deprecated for some period (as they can be modeled with explicit
getter and setter methods just as well) but have been de-deprecated
again (as they are somewhat useful when modeling old-style servi
Thomas Lange wrote:
Hi Frank,
What about an UNO interface that returns an empty reference if there is
no problem?
Interesting. This would be cheap (in success case), still allow
polymorphism, not unnecessarily burden the listener implementor ... I
like it :)
Yes, +1
module com::sun::star {
Hi Frank,
>> > What about an UNO interface that returns an empty reference if there is
>> > no problem?
>>
>> Interesting. This would be cheap (in success case), still allow
>> polymorphism, not unnecessarily burden the listener implementor ... I
>> like it :)
>
> Yes, +1
>
>> module com::sun:
Hi Eike,
> Btw, any example how the caller would actually use the Context interface
> returned? You previously described it as "the component which vetoed".
Ehm ... no. This might be a remaint in my head from the VetoException, I
just thought it might be useful, but don't have any actual use case
Hi Frank,
On Tue, May 30, 2006 at 09:56:41 +0200, Frank Schönheit wrote:
> > What about an UNO interface that returns an empty reference if there is
> > no problem?
>
> Interesting. This would be cheap (in success case), still allow
> polymorphism, not unnecessarily burden the listener implement
Eike Rathke wrote:
Hi Frank,
On Mon, May 29, 2006 at 15:33:48 +0200, Frank Schönheit wrote:
What about
struct ApprovalOrVeto_OrAnyBetterName
{
booleanIsVeto;
string Veto;
anyReason;
XInterface Context;
};
That struct would have to be created, though wit
Hi Thomas,
> What about an UNO interface that returns an empty reference if there is
> no problem?
Interesting. This would be cheap (in success case), still allow
polymorphism, not unnecessarily burden the listener implementor ... I
like it :)
So, what about
module com::sun::star {
module util
Hi,
>> What about
>>
>> struct ApprovalOrVeto_OrAnyBetterName
>> {
>> booleanIsVeto;
>> string Veto;
>> anyReason;
>> XInterface Context;
>> };
>
> That struct would have to be created, though with empty members, even in
> the all-good-no-veto case. Depend
