To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101556





------- Additional comments from [email protected] Tue Jun 23 14:45:32 +0000 
2009 -------
AW: Basic reason is that the primitive text representation used for comparing
with the old version currently still has some compromizes regarding the data
holded. In principle, a primitive should hold all data needed for it's
definition and evtl. decomposition. For text, this is not yet true: It holds a
copy of the OPO (OutlinerParaObject), but only a reference of the SdrText object
and no Information about the text attributes in the SdrObject (in it's
SfxItemSet in the range EE_ITEMS_START, EE_ITEMS_END), and no information about
the SfxItemSet's parents which define the styles.
Thus, a change in that range is not detected. Remembering the StyleSheet (or the
SfxItemSet and it's chain of parents) will not help; this will be changed
internally, but not their pointers. In Principle, a copy of the mentioned data
would be needed (i know why i avoided this for the moment).
This would also be too expensive for a 3.1.1 fix. I checked that a StyleSheet
change is detected in the model, thus the idea is now to hold a 'version number'
of the text style used at the model object. Using that version number in the
text primitive data and incrementing it when the style is changed should work
for the moment.
Added code, compiling, checking...

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to