Dag Andersen | 2 Dec 2010 10:09
Picon

Reports: problem with pageTotal()

In kplato I define a report with fields for page number (working) and total 
number of pages (not working). I specify control sources like this:
=constants.PageNumber()
=constants.PageTotal()

The page total field in the generated report shows:
constants.PageTotal()

Any hints?
--

-- 
Mvh.
Dag Andersen
Dag Andersen | 2 Dec 2010 12:58
Picon

Re: Reports: problem with pageTotal()

Torsdag 02 december 2010 10:09:30 skrev Dag Andersen:
> In kplato I define a report with fields for page number (working) and total
> number of pages (not working). I specify control sources like this:
> =constants.PageNumber()
> =constants.PageTotal()
> 
> The page total field in the generated report shows:
> constants.PageTotal()
> 
> Any hints?
Seems this was only half finished, att patch fixes it for me.
Could you commit if it is ok Jaroslaw?
--

-- 
Mvh.
Dag Andersen
Attachment (pagetotal.diff): text/x-patch, 2616 bytes
_______________________________________________
koffice-devel mailing list
koffice-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
Jaroslaw Staniek | 2 Dec 2010 13:57
Picon
Favicon
Gravatar

Re: Reports: problem with pageTotal()

On 2 December 2010 12:58, Dag Andersen <danders <at> get2net.dk> wrote:
> Torsdag 02 december 2010 10:09:30 skrev Dag Andersen:
>> In kplato I define a report with fields for page number (working) and total
>> number of pages (not working). I specify control sources like this:
>> =constants.PageNumber()
>> =constants.PageTotal()
>>
>> The page total field in the generated report shows:
>> constants.PageTotal()
>>
>> Any hints?
> Seems this was only half finished, att patch fixes it for me.
> Could you commit if it is ok Jaroslaw?

Would you like to review this, Adam?
Formally, is this patch suitable for applying to trunk or to essen?

> --
> Mvh.
> Dag Andersen
>

--

-- 
regards / pozdrawiam, Jaroslaw Staniek
 http://www.linkedin.com/in/jstaniek
 Kexi & KOffice (http://kexi-project.org, http://identi.ca/kexi,
http://koffice.org)
 KDE Software Development Platform on MS Windows (http://windows.kde.org)
_______________________________________________
koffice-devel mailing list
(Continue reading)

Dag Andersen | 2 Dec 2010 15:59
Picon

Re: Reports: problem with pageTotal()

Torsdag 02 december 2010 13:57:12 skrev Jaroslaw Staniek:
> On 2 December 2010 12:58, Dag Andersen <danders <at> get2net.dk> wrote:
> > Torsdag 02 december 2010 10:09:30 skrev Dag Andersen:
> >> In kplato I define a report with fields for page number (working) and
> >> total number of pages (not working). I specify control sources like
> >> this: =constants.PageNumber()
> >> =constants.PageTotal()
> >> 
> >> The page total field in the generated report shows:
> >> constants.PageTotal()
> >> 
> >> Any hints?
> > 
> > Seems this was only half finished, att patch fixes it for me.
> > Could you commit if it is ok Jaroslaw?
> 
> Would you like to review this, Adam?
> Formally, is this patch suitable for applying to trunk or to essen?
imvho, this is a bug as the functionallity is partially there, it just doesn't 
work. Thus it's a bug and should be fixed.
--

-- 
Mvh.
Dag Andersen
Dag Andersen | 2 Dec 2010 16:07
Picon

report chart: legend orientation

While we are at it...
I'd like to change the legend orientation to vertical. It's close to unusable 
horizontal because if you have more than one data set it will steal the page 
width.
Alternative is to position it above or below, but I think that to the right is 
best as it is now.
--

-- 
Mvh.
Dag Andersen
Björn Breitmeyer | 2 Dec 2010 16:29
Favicon

Re: report chart: legend orientation

Whats your problem with that, it can be adjusted with the chart tool.
And is otherwise document specific.
Could you provide more details.

Greetings Björn
Am Donnerstag, 2. Dezember 2010, 16:07:51 schrieb Dag Andersen:
> While we are at it...
> I'd like to change the legend orientation to vertical. It's close to
> unusable horizontal because if you have more than one data set it will
> steal the page width.
> Alternative is to position it above or below, but I think that to the right
> is best as it is now.
Adam Pigg | 2 Dec 2010 19:43
Picon

Re: report chart: legend orientation

While youre at it, can you provide some screenshots of how you are
using reports in kplato, im quite excited by it!

On Thu, Dec 2, 2010 at 3:07 PM, Dag Andersen <danders <at> get2net.dk> wrote:
> While we are at it...
> I'd like to change the legend orientation to vertical. It's close to unusable
> horizontal because if you have more than one data set it will steal the page
> width.
> Alternative is to position it above or below, but I think that to the right is
> best as it is now.
> --
> Mvh.
> Dag Andersen
>
Cyrille Berger Skott | 2 Dec 2010 20:05

KOffice/trunk freeze

Hi,

Tomorrow is RC1 time, meaning that KOffice/trunk is now deep frozen, only for 
build fixes.

I will proceed to the branching, also notice, that KOffice Group B is to be 
developed in branches/koffice-essen, and will actually moved to git on Sunday 
on a repository that will be announced on the new mailing list (if you ar not 
registered to that list, and need to know the location of the repository 
before it becomes public next week, please contact me).

For those who want to do some feature development this week end, you can use 
this command:
svn switch svn+ssh://username <at> svn.kde.org/home/kde/branches/work/koffice-essen

Or if you still want to work on bug fixes:
svn switch 
svn+ssh://username <at> svn.kde.org/home/kde/branches/koffice/2.3/koffice

(This command will not work until tomorrow after the branching)

--

-- 
Cyrille Berger Skott
Adam Pigg | 3 Dec 2010 07:32
Picon

Re: Reports: problem with pageTotal()

Unfortunately, i didnt have a lot of time last night to look at it.

On first glance, it seems the new code may be much slower when there
are lots of pages/objects, as it loops over every object in every page
looking for ones that require post-processing.  The old (commented)
code  created a list of objects requiring post-processing, as this is
likely to be ~no-pages.

Could you try for something like this before the freeze, or i can have
a go this evening.  If not, it could go into trunk like this, as its
probably better working than not, and can be sped up later.

Cheers

Adam

On Thu, Dec 2, 2010 at 2:59 PM, Dag Andersen <danders <at> get2net.dk> wrote:
> Torsdag 02 december 2010 13:57:12 skrev Jaroslaw Staniek:
>> On 2 December 2010 12:58, Dag Andersen <danders <at> get2net.dk> wrote:
>> > Torsdag 02 december 2010 10:09:30 skrev Dag Andersen:
>> >> In kplato I define a report with fields for page number (working) and
>> >> total number of pages (not working). I specify control sources like
>> >> this: =constants.PageNumber()
>> >> =constants.PageTotal()
>> >>
>> >> The page total field in the generated report shows:
>> >> constants.PageTotal()
>> >>
>> >> Any hints?
>> >
(Continue reading)

Dag Andersen | 3 Dec 2010 08:38
Picon

Re: Reports: problem with pageTotal()

Fredag 03 december 2010 07:32:27 skrev Adam Pigg:
> Unfortunately, i didnt have a lot of time last night to look at it.
> 
> On first glance, it seems the new code may be much slower when there
> are lots of pages/objects, as it loops over every object in every page
> looking for ones that require post-processing.  The old (commented)
> code  created a list of objects requiring post-processing, as this is
> likely to be ~no-pages.
> 
> Could you try for something like this before the freeze, or i can have
> a go this evening.  If not, it could go into trunk like this, as its
> probably better working than not, and can be sped up later.
New patch follows.
This one registers primitives that needs post processing with the ORODocument, 
so should be as fast as possible.
> 
> Cheers
> 
> Adam
> 
> On Thu, Dec 2, 2010 at 2:59 PM, Dag Andersen <danders <at> get2net.dk> wrote:
> > Torsdag 02 december 2010 13:57:12 skrev Jaroslaw Staniek:
> >> On 2 December 2010 12:58, Dag Andersen <danders <at> get2net.dk> wrote:
> >> > Torsdag 02 december 2010 10:09:30 skrev Dag Andersen:
> >> >> In kplato I define a report with fields for page number (working) and
> >> >> total number of pages (not working). I specify control sources like
> >> >> this: =constants.PageNumber()
> >> >> =constants.PageTotal()
> >> >> 
> >> >> The page total field in the generated report shows:
(Continue reading)


Gmane