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





------- Additional comments from [email protected] Tue Sep  8 09:19:13 +0000 
2009 -------
Now I'm really confused, especially because of fs's comment (desc19).
If the problem also applies to Basic macros I don't think that it is
really covered by this issue.

mav send this issue to me with an attached sample document and in
his comment (desc11) he described that the BasicContainer gets modi-
fied without really being modified. mav's sample document doesn't
contain any Basic and I found that Basic gets modified because the
Standard library is created internally when hasBasic() is called.

So my comment (desc12) isn't misleading, it just describes the only
problem that is covered by mav's comment and sample. And this pro-
blem indeed only occurs for documents containing signed scripts but
no Basic scripts (which by the way could easily be worked around by
just adding an empty Basic library).

That was and still is my level of knowledge concerning this problem
and nobody had objected until now. So I wonder what exactly is cove-
red by cws encsig09 and what the successor issue 104876 is about.
If also documents containing Basic are affected there must be ano-
ther completely different bug mechanism that hasn't been visible
for me so far. I also need another sample document then for i104876.

Can anyone please help me to reduce my confusion... :-)


---------------------------------------------------------------------
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