Skip Menu |

This queue is for tickets about the Spreadsheet-WriteExcel CPAN distribution.

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::WriteExcel here are some pointers

1) State the issues as clearly and as concisely as possible. A simple program or Excel test file (see below) will often explain the issue better than a lot of text.

2) Provide information on your system, version of perl and module versions. The following program will generate everything that is required. Put this information in your bug report.

    #!/usr/bin/perl -w

    print "\n    Perl version   : $]";
    print "\n    OS name        : $^O";
    print "\n    Module versions: (not all are required)\n";

    my @modules = qw(
                      Spreadsheet::WriteExcel
                      Parse::RecDescent
                      File::Temp
                      OLE::Storage_Lite
                      IO::Stringy
                      Spreadsheet::ParseExcel
                      Scalar::Util
                      Unicode::Map
                    );

    for my $module (@modules) {
        my $version;
        eval "require $module";

        if (not $@) {
            $version = $module->VERSION;
            $version = '(unknown)' if not defined $version;
        }
        else {
            $version = '(not installed)';
        }

        printf "%21s%-24s\t%s\n", "", $module, $version;
    }

    __END__

3) Upgrade to the latest version of Spreadsheet::WriteExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.

4) Create a small but complete example program that demonstrates your problem. The program should be as small as possible. At the same time it should be a complete program that generates an Excel file. If the Spreadsheet::WriteExcel section is part of a much larger program then simplify it down to the essentials. Simulate any DB reads with an array.

5) Say if you tested with Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

6) If you are submitting a patch you should check with the author whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.

Asking a question

If you would like to ask a more general question there is the Spreadsheet::WriteExcel Google Group.

Report information
The Basics
Id: 63348
Status: resolved
Priority: 0/
Queue: Spreadsheet-WriteExcel

People
Owner: Nobody in particular
Requestors: mr [...] netadair.de
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 2.37
Fixed in: (no value)



Subject: write_comment interaction with reformatting (probably affects bitmaps as well)
When a comment is added, the current boundary is calculated from given parameters and worksheet cell widths etc. When the cells neighboring the commented cell, i.e. the ones covered by the visible comment box, are reformatted in width or height, the once calculated boundaries are not valid anymore and e.g. zero-width comment boxes show up in Excel. Maybe this can be commented in the docs as a NB; it took me some time to find out. Maybe it can be fixed by automatically postponing boundary calculation up to a certain point in time or repeat it before writing the Excel? This is what I have done in my code now to resolve that issue.
On Fri Nov 26 05:24:25 2010, mr@netadair.de wrote: Show quoted text
> When a comment is added, the current boundary is calculated from given > parameters and worksheet cell widths etc. > When the cells neighboring the commented cell, i.e. the ones covered by > the visible comment box, are reformatted in width or height, the once > calculated boundaries are not valid anymore and e.g. zero-width comment > boxes show up in Excel. > Maybe this can be commented in the docs as a NB; it took me some time to
Hi, This is documented (at least if I have understood the issue correctly) See the "Note about row height and comments" paragraph in the write_comment() docs: http://search.cpan.org/dist/Spreadsheet-WriteExcel/lib/Spreadsheet/WriteExcel.pm#write_comment%28$row,_$column,_$string,_...%29 John. --
P.S. If I haven't understood the issue correctly could you submit a small, self contained, example program that demonstrates the issue along the lines of the following guidelines: https://rt.cpan.org/Dist/Display.html?Queue=Spreadsheet-WriteExcel John. --
Closed. Documented feature.