Re: [PythonReports-users] Column / label issue

[alexander s. <al...@go...>]

On 21.03.2013 13:18, Werner F. Bruhin wrote:
>
> The problem was if I defined a top margin on the report then the second
> column would align to high (when looking at the generated PDF), so I set
> the top margin on the report to zero and set the "top margin" as the
> column header hight and now things align correctly.

I have fixed it now.  Thank you for reporting.

> Where would you set the 'eject' to indicate to go to the next label
> column?   Setting it on the footer seems to work for me, i.e. on my 2
> columns with 6 labels each, it prints the 6 labels in the first column
> and then goes to the second column.

The logic, in simplified words, is this:

- if there is not enough space for next details section, we end current 
page/column and start a new one.

- when we end a page or column, we print respective footer.

So, when a footer is built, you already are in the middle of eject 
sequence.  Doing another eject here, if it was processed, would make 
next column entirely blank.  That makes no sense, so the scheme for 
headers and footers does not include eject elements, and they are 
ignored as unknown.

The eject element is meant to end a column or page prematurely, when 
there still is enough space for more items.  (And sometimes when the 
builder is not smart enough to figure out requirements for complex 
templates.)  For example, you may want to start each vintage on a new 
page.  If you have no things like that, you do not need to use eject 
element.

> Which is fine with me, also I  would prefer that it would do
> column 1, row 1, column 2 row 1, column 1 row 2 etc etc

That's simple.  Make your reporting sequence contain pairs: [(item1, 
item2), (item3, item4), ...] - and draw a template for two items side by 
side.

Best wishes,
alex.