From: Werner F. Bruhin <werner.bruhin@fr...> - 2013-03-20 13:52:24
On 20/03/2013 11:18, Werner F. Bruhin wrote:
> I am trying to do some labels, started with an A5 version which has 2
> As you can see from the attached the second column is not correctly
> aligned, i.e. it starts a bit too high.
It looks like the second column does not shift down by the top margin.
Hhm, set top margin to zero, activated column header and set the top
margin value for the height of the column header and things are aligned.
From: alexander smishlajev <alex@go...> - 2013-03-21 11:02:55
On 20.03.2013 15:54, Werner F. Bruhin wrote:
>> I am trying to do some labels, started with an A5 version which has 2
>> As you can see from the attached the second column is not correctly
>> aligned, i.e. it starts a bit too high.
> It looks like the second column does not shift down by the top margin.
> Hhm, set top margin to zero, activated column header and set the top
> margin value for the height of the column header and things are aligned.
I am sorry, Werner, I fail to understand what the issue is all about.
Do you mean editor interface, or printout building, or what?
P.S. By the way, why do you need eject in a footer? I'm not sure it is
processed in any way.
From: alexander smishlajev <alex@go...> - 2013-03-24 12:56:28
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
> 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