[Libreoffice] Issues for pivot tables ... where to post

Kohei Yoshida kyoshida at novell.com
Fri Feb 11 08:02:24 PST 2011

On Fri, 2011-02-11 at 11:47 +0100, Cor Nouws wrote:
> Hi Kohei,
> Kohei Yoshida wrote (08-02-11 16:10)
> > On Tue, 2011-02-08 at 13:23 +0100, Cor Nouws wrote:
> >> Someone writes about an issue in OOo/Lo 330, that was not present in OOo
> >> 321.
> >>
> >> Is it better to post that in Bugzilla or in the OOo IssueTracker?
> >> (Currently I see one Pivot-issue - 33990 - in Bugzilla)
> >
> > Let's put it in our bugzilla, and please assign that directly to me.
> OK, done (thanks to Joop Bukker too)
> https://bugs.freedesktop.org/show_bug.cgi?id=34107
> > I'm working on the data pilot code right now to fix several issues I
> > discovered have been broken since 3.3.  So, it's nice to know any
> > regressions to data pilot while I'm at it.
> 1st item is a difference between OOo and LibO

Yes, and that's an enhancement not a bug.  A lot of folks didn't like
the idea that OOo created table right below the data grid.

> 2nd a common issue, not a regression.

Regarding this, the data pilot table expects a full absolute reference,
including the sheet name ($Sheet.$A$1), which means you can't type a
relative address such as F1.  Other dialogs expecting an address
probably has the same limitation (e.g. Goal Seek dialog).

Having said that, we may be able to enhance that to take a relative
address from the UI.  Let me look into that and see how easy or
difficult that will be.

> [ wrt the differences OOo / LibO: is there an overview of those, or if 
> not, a pointer how to gain that information?

I'm afraid there is no overview unless someone spends time to create
one, either from memory, by asking, or manually checking the git commit
records.  And as we grow further apart from OOo that will only become
more difficult.

So, I think the best way for now is to ask us weather the difference is
intended, or unintended, on a case-by-case basis (just like you did).

Another option is to go into the source code, find the relevant code,
and check the git history.  But this may or may not be easier than the
above options depending on how comfortable you are with going through
the source tree. ;-)



Kohei Yoshida, LibreOffice hacker, Calc
<kyoshida at novell.com>

More information about the LibreOffice mailing list