GNOME Bugzilla – Bug 521726
many rows of empty cells created when exporting to text
Last modified: 2008-09-12 05:07:10 UTC
Please describe the problem: Whenever there's a graph in a preceding sheet, when data is exported to a text file, empty rows are created in the text file before the intended data. Steps to reproduce: 1. Create a new Gnumeric workbook 2. Insert data in the second sheet 3. Create a graph in the first sheet 4. export the data from the second sheet to a configurable text format file Actual results: The intended data in the created text file is not in the same rows as in the source sheet, but further down in the sheet. That is, new rows were created preceding the data. Expected results: The destination file should look exactly like the source sheet. Does this happen every time? Yes. Other information:
I can't replicate this. Could you provide a copy of a workbook in which you observe this problem? Thanks
Created attachment 107091 [details] source file the intended export is the data in row 1 and 2 in the "data" sheet.
Created attachment 107092 [details] destination file 33 new rows were added in the destination file before the data we intended to save
I am attaching both sample source .gnumeric file and sample target .txt file with the issue. Scroll down that one to find the source data, many rows below. The more graphs one adds to the first sheet, the more rows are added in the text file. I also forgot to mention: I export to Macintosh line termination, and use semicolon as separator.
Now I can replicate: it is essential that there is no data on the first sheet (the sheet with graphics) at all. Otherwise you get a dialog in which you can choose which sheets to export. Gnumeric realizes that there is nothing to export on the first sheet, but keeps the sheet marked for export. Later it exports the range of empty cells that is covered by the graphs.
Still present in 1.9.0...
I thought I had fixed that already... This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Are you sure Andreas? I still see it in 1.9.2...
I guess, I wasn't clear enough: I thought I had fixed it. I determined that I didn't. So I fixed it before adding that comment #7. It will be in 1.9.3. (it really consisted of adding "&& !empty" to a single source code line.