|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.2.2
|
| Fix Version/s: |
2.0
|
|
|
There are several bugs in AbstractExportFileType.
exportToFile(File, Component[],Component,Properties,String)
(and the stream version) calls startExport (before setting multipage, which is also an error) and then starts a MultiPageSingleFileExportThread, which calls startExport again! The result is an invalid file with two headers.
Also, the thread calls openPage for every page, including the first. But at least for postscript, writeProlog (called indirectly by startExport) calls openPage, so the first page is already open.
|
|
Description
|
There are several bugs in AbstractExportFileType.
exportToFile(File, Component[],Component,Properties,String)
(and the stream version) calls startExport (before setting multipage, which is also an error) and then starts a MultiPageSingleFileExportThread, which calls startExport again! The result is an invalid file with two headers.
Also, the thread calls openPage for every page, including the first. But at least for postscript, writeProlog (called indirectly by startExport) calls openPage, so the first page is already open. |
Show » |
|
Bug
Resolved
Major
Exporting array of components produces bad file
The last paragraph of my bug report was incorrect. It only does that if startExport is called before multipage is set, which causes other problems anyway.
I guess the documaentation shoud say that multipage shouldnt be changed after startExport, but that's sort of obvious.