Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

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

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::ParseExcel 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::ParseExcel
                      Scalar::Util
                      Unicode::Map
                      Spreadsheet::WriteExcel
                      Parse::RecDescent
                      File::Temp
                      OLE::Storage_Lite
                      IO::Stringy
                    );

    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::ParseExcel (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 example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.

5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly: jmcnamara@cpan.org

6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

7) If you are submitting a patch you should check with the maintainer 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::ParseExcel Google Group.

Report information
The Basics
Id: 43042
Status: open
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: cap10morgan [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.49
Fixed in: (no value)



Subject: row_range returns erroneous results when CellHandler is being used
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Type: text/plain
Charset: utf8
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 334
Download (untitled) / with headers
text/plain 334b
When CellHandler is set in the constructor, subsequent calls to row_range return erroneous results. This appears to be due to the fact that it assumes you're parsing the entire worksheet before calling row_range, which is not the case when using the CellHandler callback. This is on Mac OS X Leopard using Perl 5.8.8 from MacPorts.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-29719-1233827268-215.43042-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 391
Download (untitled) / with headers
text/plain 391b
On Wed Feb 04 21:12:13 2009, cap10morgan wrote: Show quoted text
> When CellHandler is set in the constructor, subsequent calls to > row_range return erroneous > results.
Hi, Thanks for that. Could you post an example spreadsheet and program. See the following for some information on what to include to help debugging: http://rt.cpan.org/Public/Dist/Display.html?Name=Spreadsheet-ParseExcel John. --
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-29719-1233827268-215.43042-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Charset: utf8
References: <rt-3.6.HEAD-29719-1233827268-215.43042-0-0 [...] rt.cpan.org>
Content-Type: multipart/mixed; boundary="----------=_1233853518-4331-306"
Message-ID: <rt-3.6.HEAD-4331-1233853518-795.43042-0-0 [...] rt.cpan.org>
From: cap10morgan [...] gmail.com
X-RT-Original-Encoding: utf-8
Content-Length: 0
Content-Disposition: inline
Content-Type: text/plain
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 666
Download (untitled) / with headers
text/plain 666b
On Thu Feb 05 04:47:48 2009, JMCNAMARA wrote: Show quoted text
> On Wed Feb 04 21:12:13 2009, cap10morgan wrote:
> > When CellHandler is set in the constructor, subsequent calls to > > row_range return erroneous > > results.
> > Hi, > > Thanks for that. > > Could you post an example spreadsheet and program. See the following for > some information on what to include to help debugging: > > http://rt.cpan.org/Public/Dist/Display.html?Name=Spreadsheet-ParseExcel > > John.
Sure, no problem. Just unzip the attachment and run ./spreadsheet-parseexcel-bug.pl spreadsheet-parseexcel-bug.xls to see the bug in action. Let me know if you need anything else to help squash it. :)
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Type: multipart/mixed; boundary="----------=_1233853517-4331-305"
Charset: utf8
Content-Length: 0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: iso-8859-1
Content-Length: 0
Content-Type: application/zip; name="spreadsheet-parseexcel-bug.zip"
Content-Disposition: inline; filename="spreadsheet-parseexcel-bug.zip"
Content-Transfer-Encoding: base64
Content-Length: 12002

Message body not shown because it is not plain text.

MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-4331-1233853518-795.43042-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <rt-3.6.HEAD-29719-1233827268-215.43042-0-0 [...] rt.cpan.org> <rt-3.6.HEAD-4331-1233853518-795.43042-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-29719-1233854616-734.43042-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 455
Download (untitled) / with headers
text/plain 455b
On Thu Feb 05 12:05:18 2009, cap10morgan wrote: Show quoted text
> run ./spreadsheet- parseexcel-bug.pl > spreadsheet-parseexcel-bug.xls to see the bug in action. Let me know > if you need anything else to help squash it. :)
Hi, Hmmm, I'd like to argue that it isn't a bug and that it probably isn't wise to mix post-parsing functions into the parsing phase. However, it will probably just be quicker to fix it. :-) Look out for a fix in the next release. John. --
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-29719-1233854616-734.43042-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <rt-3.6.HEAD-29719-1233827268-215.43042-0-0 [...] rt.cpan.org> <rt-3.6.HEAD-4331-1233853518-795.43042-0-0 [...] rt.cpan.org> <rt-3.6.HEAD-29719-1233854616-734.43042-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-4331-1233856904-445.43042-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 964
Download (untitled) / with headers
text/plain 964b
On Thu Feb 05 12:23:36 2009, JMCNAMARA wrote: Show quoted text
> On Thu Feb 05 12:05:18 2009, cap10morgan wrote:
> > run ./spreadsheet- parseexcel-bug.pl > > spreadsheet-parseexcel-bug.xls to see the bug in action. Let me know > > if you need anything else to help squash it. :)
> > Hi, > > Hmmm, I'd like to argue that it isn't a bug and that it probably isn't > wise to mix post-parsing functions into the parsing phase. > > However, it will probably just be quicker to fix it. :-) > > Look out for a fix in the next release. > > John.
Yeah, that makes sense. If it helps, my use case is that before I switched to the event-driven model (i.e. CellHandler), I was using the row_range values to create a progress bar to give some visual feedback to the user. Obviously that's mostly necessary when dealing with large spreadsheets, but large spreadsheets are also when you most need to use CellHandler and NotSetCell. :) Glad to hear there will be a fix coming. Thanks!
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-4331-1233853518-795.43042-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <rt-3.6.HEAD-29719-1233827268-215.43042-0-0 [...] rt.cpan.org> <rt-3.6.HEAD-4331-1233853518-795.43042-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-3003-1394558048-257.43042-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 515
Download (untitled) / with headers
text/plain 515b
On Thu Feb 05 12:05:18 2009, cap10morgan wrote: Show quoted text
> > Sure, no problem. Just unzip the attachment and run ./spreadsheet- > parseexcel-bug.pl > spreadsheet-parseexcel-bug.xls to see the bug in action. Let me know > if you need anything > else to help squash it. :)
MaxRow is updated as the worksheet is parsed, so I don't see this getting fixed. If you can devise a way to tell what the MaxRow is before parsing the worksheet data, let me know and I'll fix it, otherwise I'll probably reject this issue eventually.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.