Raimondo Giammanco added the comment:
hit F9 ?!?
I feel ashamed. The need to recalculate the fields simply slipped my mind.
Of course, in some way Writer has to be told about the strings replacement.
Maybe could my fault be partially justifiable if one consider the autoupdate
behaviour with
R. David Murray added the comment:
So if I'm understanding correctly the python update to the file happens
correctly in both cases, and the issue with the update not being immediately
visible is an issue on the OpenOffice side of things. So I'm closing this as a
3rd party bug (though it
SilentGhost added the comment:
Whether for reasons of slightly different setup or due to something else, I'm
not able to reproduce the issue. What I do see, is that the field is not
automatically updated, so on opening of the document I have to hit F9 to get
the answer field updated. That
New submission from Raimondo Giammanco:
Steps to reproduce
¯¯
-1- Create a document.odt containing an input (text) field and a conditional
text field; the latter will show a different text based upon the content of the
input text field. [use attached example.odt]
-2- Edit the
SilentGhost added the comment:
Raimondo, the documentation clearly states that the compression method is
either inherited from ZipInfo instance (when that one is passed) or set to
ZIP_STORED otherwise. Since you're not passing ZipInfo instance, but the string
(as the first argument to
Raimondo Giammanco added the comment:
SilentGhost, thank you for your reply but I am probably missing something with
it. Maybe there is some misunderstanding because of my unclear report. Please
let me sum up my point and excuse some repetitiveness
From the documentation of .writestr:
``If
