[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Question regarding gb.report2
[Thread Prev] | [Thread Next]
- Subject: Re: Question regarding gb.report2
- From: Greg Raffaelle <greg.raffaelle@xxxxxxxxx>
- Date: Tue, 21 Oct 2025 08:14:08 -0500
- To: user@xxxxxxxxxxxxxxxxxxxxxx
I installed the latest gambas3 update version 3.21.0 and the issue I was having with the report component moving the start of the second table to a new page is resolved. It now works the same for me as other users have reported. So thanks everyone for the help. Unfortunately, I was doing some further testing with the same example program I sent to see what would happen with different number of lines in the two tables. I think I found an issue with report. When the first table is long and continues on the second page, the second table's heading and top padding are cut off. See the attached pdf. This does not happen when the first table is short and stays on the first page. When the first table is really long and runs on to the third page, the heading, top padding, and first line of the second table are cut off. (see pdf in next email). For each additional page the first table grows is length another line of the second table is cut off. Thanks for your further assistance. Greg On Mon, Oct 20, 2025 at 11:20 AM Benoît Minisini < benoit.minisini@xxxxxxxxxxxxxxxx> wrote: > Le 20/10/2025 à 14:48, Greg Raffaelle a écrit : > > Below is my system information. I see wayland under platform. Is > > wayland my problem? > > > > Wayland is not your problem. Wayland is the problem of everyone. :-) > > -- > Benoît Minisini. > > >
Attachment:
SecondPage
Description: Binary data
| Re: Question regarding gb.report2 | BB <adamnt42@xxxxxxxxx> |
| Re: Question regarding gb.report2 | Fabien Bodard <gambas.fr@xxxxxxxxx> |
| Re: Question regarding gb.report2 | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
| Re: Question regarding gb.report2 | Greg Raffaelle <greg.raffaelle@xxxxxxxxx> |
| Re: Question regarding gb.report2 | Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> |