[Libreoffice] [PUSHED] Re: [REVIEW-3.5] Handling ordering problem when properties are set one by one

Michael Stahl mstahl at redhat.com
Tue Jan 24 07:45:16 PST 2012

On 24/01/12 16:12, Lubos Lunak wrote:
> On Tuesday 24 of January 2012, Michael Stahl wrote:
>> On 23/01/12 21:31, Lubos Lunak wrote:

>>>  It seems to be quite a common way for LO code to use this
>>> let's-push-all-the-data-as-properties-one-by-one approach, so I wonder
>>> what the common way of avoiding this problem is? Preferably something
>>> that's not an ugly hack, excuse the naivety.
>> i'm not aware of a general solution for this problem; i'm afraid if
>> there are good reasons not do a change as above, then ugly hack is in
>> order...  i don't remember running into such a problem before, probably
>> this kind of dependency is quite rare.
>  I've eventually settled on db0f839920c38973f8448df0f74de7c4c95c832c , could 
> somebody review and push to 3.5?

that shouldn't break anything, pushed:


More information about the LibreOffice mailing list