File foo.ods with chart,
- switch into chart edit mode
- then Save As
- name testChart choose extension odc
> Error saving the document foo.ods (!)
The operation was started under an invalid parameter
> no odc export
Verified with Windows 7 64bits &
Build ID: 36b5efd733c68c67bb4a1b9489a775aed1fe98e
TinderBox: Win-x86_9-Voreppe, Branch:libreoffice-4-1, Time: 2013-05-31_17:43:42
adding markus to CC. Should have done that immediately. Sorry.
I can't reproduce this problem. Can you please add a test document (ods) plus a detailed instruction.
The Save As dialog should only have ODC as file extension so I have no idea what you mean with "choose extension odc" as this is already done by the dialog.
hmm, strange. It does work for me now.
I think to remember there were two choices in the file type list. Maybe there was something strange because I tried to fiend a way to export via a different route first??
@pierre-yves: what is the situation with you?
(In reply to comment #4)
> @pierre-yves: what is the situation with you?
As Markus said, there is only one option available
I struggled today to reproduce the problem.
I think I found the procedure. The error occurs when there is more than one spreadsheet open.
1. File> Open> ExportODC1.ods (attachment)
2. File> Open> ExportODC2.ods (attachment)
3. Edit chart (double-click on the chart)
4. File> Save as (dialog opens with the selected type ODC)
5. Give a name and confirm
The error message occurs (see attached screenshot)
Created attachment 80280 [details]
Created attachment 80281 [details]
Created attachment 80282 [details]
Removed the feature from the advertised list and will hide it in dbgutil builds. I'm sorry but it is not stable enough for use right now.
I'm seeing this now with 220.127.116.11
"Error saving the document ...:
The operation was started under an invalid parameter."
Why is marked as wontfix?
I will close this, because the state of the issue is unclear.
The problem still exists in current versions and is tracked in bug 93005.
*** This bug has been marked as a duplicate of bug 93005 ***