Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2018-02

fpreport designer

15 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

patspiper

Hi,

I am able to create fpreports by code.

However the graphical designer is riddled with serious bugs making it impossible to use. I haven't succeeded in creating a single report. Is something wrong with my installation, or is the designer still in alpha stage? I'll create bug reports if it's the latter case.

Stephano

Reply by email

Michael Van Canneyt
to patspiper
patspiper wrote 8 lines
Hi, I am able to create fpreports by code. However the graphical designer is riddled with serious bugs making it impossible to use. I haven't succeeded in creating a single report. Is something wrong with my installation, or is the designer still in alpha stage? I'll create bug reports if it's the latter case.

Hm.
I don't know your installation of course, so it is hard to comment on that.

But you should definitely be able to make reports. I know I do. But then, I made it, so I will probably avoid doing things that confuse the designer...

If you do experience bugs, please report them, I will do my best to fix them ASAP.

Michael.

Reply by email

patspiper
to Michael Van Canneyt
Michael Van Canneyt wrote 19 lines
On Sun, 25 Feb 2018, patspiper via Lazarus wrote: > Hi, > > I am able to create fpreports by code. > > However the graphical designer is riddled with serious bugs making it > impossible to use. I haven't succeeded in creating a single report. > Is something wrong with my installation, or is the designer still in > alpha stage? I'll create bug reports if it's the latter case. Hm. I don't know your installation of course, so it is hard to comment on that. But you should definitely be able to make reports. I know I do. But then, I made it, so I will probably avoid doing things that confuse the designer... If you do experience bugs, please report them, I will do my best to fix them ASAP.

I use FPC 3.0.5 with fpreport from trunk along with lazarus trunk.

Just to test the waters:

1- Create a new application
2- Place a TFPReport on the form
3- Double click the FPReport component to open the designer 4- Add a page by clicking the add page toolbutton
-> Bug1: The page properties are not displayed in the designer's object inspector
5- Add a databand and enlarge it
6- Click on memo toolbutton
7- Click on the databand without dragging. The memo will be created with 0 size.
8- Resize the memo with the mouse
-> Bug2: The designer freezes and cannot be closed anymore

If you can confirm these 2 bugs, i'll start creating bug reports in the tracker.

Stephano

Reply by email

Andreas Frieß
to patspiper

Actual it make IMHO only sense with the actual trunk fpc (and trunk Lazarus). Pls use the standalone designer too, to make a check if the problem is not only in the fp-report component.

Andreas

patspiper wrote 42 lines
On 25/02/18 21:09, Michael Van Canneyt via Lazarus wrote: > On Sun, 25 Feb 2018, patspiper via Lazarus wrote: >> Hi, >> >> I am able to create fpreports by code. >> >> However the graphical designer is riddled with serious bugs making >> it impossible to use. I haven't succeeded in creating a single >> report. Is something wrong with my installation, or is the designer >> still in alpha stage? I'll create bug reports if it's the latter case. > > Hm. I don't know your installation of course, so it is hard to > comment on that. > > But you should definitely be able to make reports. I know I do. But > then, I made it, so I will probably avoid doing things that confuse > the designer... > > If you do experience bugs, please report them, I will do my best to > fix them ASAP. I use FPC 3.0.5 with fpreport from trunk along with lazarus trunk. Just to test the waters: 1- Create a new application 2- Place a TFPReport on the form 3- Double click the FPReport component to open the designer 4- Add a page by clicking the add page toolbutton -> Bug1: The page properties are not displayed in the designer's object inspector 5- Add a databand and enlarge it 6- Click on memo toolbutton 7- Click on the databand without dragging. The memo will be created with 0 size. 8- Resize the memo with the mouse -> Bug2: The designer freezes and cannot be closed anymore If you can confirm these 2 bugs, i'll start creating bug reports in the tracker. Stephano

Reply by email

Michael Van Canneyt
to Andreas Frieß

Hi,

1. Agreed about the use of trunk FPC/lazarus.

2. In the standalone designer, I can reproduce the bug in step 8, but not the one in step 4.

3. In view of point 2, please report bugs.

Michael.

Andreas Frieß wrote 57 lines
Actual it make IMHO only sense with the actual trunk fpc (and trunk Lazarus). Pls use the standalone designer too, to make a check if the problem is not only in the fp-report component. Andreas Am 25.02.2018 um 20:33 schrieb patspiper via Lazarus: > On 25/02/18 21:09, Michael Van Canneyt via Lazarus wrote: >> On Sun, 25 Feb 2018, patspiper via Lazarus wrote: >>> Hi, >>> >>> I am able to create fpreports by code. >>> >>> However the graphical designer is riddled with serious bugs making >>> it impossible to use. I haven't succeeded in creating a single >>> report. Is something wrong with my installation, or is the designer >>> still in alpha stage? I'll create bug reports if it's the latter case. >> >> Hm. I don't know your installation of course, so it is hard to >> comment on that. >> >> But you should definitely be able to make reports. I know I do. But >> then, I made it, so I will probably avoid doing things that confuse >> the designer... >> >> If you do experience bugs, please report them, I will do my best to >> fix them ASAP. > > I use FPC 3.0.5 with fpreport from trunk along with lazarus trunk. > > Just to test the waters: > > 1- Create a new application > 2- Place a TFPReport on the form > 3- Double click the FPReport component to open the designer > 4- Add a page by clicking the add page toolbutton > -> Bug1: The page properties are not displayed in the designer's > object inspector > 5- Add a databand and enlarge it > 6- Click on memo toolbutton > 7- Click on the databand without dragging. The memo will be created > with 0 size. > 8- Resize the memo with the mouse > -> Bug2: The designer freezes and cannot be closed anymore > > If you can confirm these 2 bugs, i'll start creating bug reports in > the tracker. > > Stephano -- _______________________________________________ Lazarus mailing list https://lists.lazarus-ide.org/listinfo/lazarus

Reply by email

patspiper
to Michael Van Canneyt
Michael Van Canneyt wrote
1. Agreed about the use of trunk FPC/lazarus.

I can't build the Lazarus IDE with FPC trunk because of an FPC bug (#33230) that makes a package fail to compile.

2. In the standalone designer, I can reproduce the bug in step 8, but not the one in step 4.

I will use the standalone designer (with FPC trunk) for the time being.

For step 4, add the page right after firing the designer (don't create a new report). Refer to bug report #33234.

I will proceed with creating bug reports. However, the bug tracker lacks an fpreport category. I am currently filing the bugs under packages.

Stephano

Reply by email

Andreas Frieß
to patspiper

Acknowledge of the two Bugs

-> Bug1: The page properties are not displayed in the designer's object inspector
-> Bug2: The designer freezes and cannot be closed anymore

i can reproduce this with actual trunk fpc/ trunk Lazarus.

Another goal is, if you install lazideintfreport, the lazarus won't start without a message, if you switch logging on, you find the reason: freetype-56.dll is missing. The problem is, you have NO indication, no messagebos, nothing, why Lazarus wont start and exit immedatly.

sing config file C:\Data\lazdev\trunk_trunk\lazarus\lazarus.cfg [FORMS.PP] ExceptionOccurred
  Sender=EInOutError
  Exception=Can not load Freetype library "freetype-6.dll". Check your installation.
  Stack trace:
  $00E41D99  INITIALIZEFREETYPE,  line 529 of
./fcl-image/src/libfreetype.inc
  $00E41E1D  INITIALIZEFREETYPE,  line 536 of
./fcl-image/src/libfreetype.inc
  $00E41E9A  FREETYPEHDYN_$$_init$,  of ./fcl-image/src/libfreetype.inc TApplication.HandleException Can not load Freetype library "freetype-6.dll". Check your installation.
  Stack trace:
  $00E41D99  INITIALIZEFREETYPE,  line 529 of
./fcl-image/src/libfreetype.inc
  $00E41E1D  INITIALIZEFREETYPE,  line 536 of
./fcl-image/src/libfreetype.inc
  $00E41E9A  FREETYPEHDYN_$$_init$,  of ./fcl-image/src/libfreetype.inc

Andreas

patspiper wrote 18 lines
On 26/02/18 19:27, Michael Van Canneyt via Lazarus wrote: > 1. Agreed about the use of trunk FPC/lazarus. I can't build the Lazarus IDE with FPC trunk because of an FPC bug (#33230) that makes a package fail to compile. > 2. In the standalone designer, I can reproduce the bug in step 8, but > not the one in step 4. I will use the standalone designer (with FPC trunk) for the time being. For step 4, add the page right after firing the designer (don't create a new report). Refer to bug report #33234. I will proceed with creating bug reports. However, the bug tracker lacks an fpreport category. I am currently filing the bugs under packages. Stephano

Reply by email

Andreas Frieß
to Andreas Frieß

The second bug is in the standalone-designer too.

Andreas

Andreas Frieß wrote 7 lines
Acknowledge of the two Bugs -> Bug1: The page properties are not displayed in the designer's object inspector -> Bug2: The designer freezes and cannot be closed anymore i can reproduce this with actual trunk fpc/ trunk Lazarus.

Reply by email

patspiper
to Andreas Frieß
Andreas Frieß wrote
The second bug is in the standalone-designer too. Andreas

I have created 8 bug reports.

Just to make sure: Once i create report data (SQLDB/firebird) as Data1. I cannot set the page or the databand Data property to Data1. Data1 is the the OI Data property dropdown, but it will not persist and the entry will stay blank. Clicking on the preview icon freezes the designer.

What are be the right steps for data?

Stephano

Reply by email

Michael Van Canneyt
to patspiper
patspiper wrote 12 lines
On 26/02/18 20:07, Andreas Frieß via Lazarus wrote: > The second bug is in the standalone-designer too. > > Andreas I have created 8 bug reports. Just to make sure: Once i create report data (SQLDB/firebird) as Data1. I cannot set the page or the databand Data property to Data1. Data1 is the the OI Data property dropdown, but it will not persist and the entry will stay blank. Clicking on the preview icon freezes the designer. What are be the right steps for data?

These are the right steps. The data is set.

The problem is in my misunderstanding how the OI works. For some reason, it refuses to display component references - even though they are set - if the component does not include csDesigning in the component state. I fixed that.

All reported bugs and feature requests except 1 should now be fixed, I also made some other improvements.

Make sure you update the FPC repository, some changes to the base classes were needed.

Thanks for reporting the bugs !

Michael.

Reply by email

patspiper
to Michael Van Canneyt
Michael Van Canneyt wrote 17 lines
On Mon, 26 Feb 2018, patspiper via Lazarus wrote: > Just to make sure: Once i create report data (SQLDB/firebird) as > Data1. I cannot set the page or the databand Data property to Data1. > Data1 is the the OI Data property dropdown, but it will not persist > and the entry will stay blank. Clicking on the preview icon freezes > the designer. > > What are be the right steps for data? These are the right steps. The data is set. The problem is in my misunderstanding how the OI works. For some reason, it refuses to display component references - even though they are set - if the component does not include csDesigning in the component state. I fixed that.

I still can't set the Data and ChildBand properties. I updated fpc trunk and lazarus and am testing using the standalone designer.

Show quoted text 8 lines
All reported bugs and feature requests except 1 should now be fixed, I also made some other improvements. Make sure you update the FPC repository, some changes to the base classes were needed. Thanks for reporting the bugs !

Thanks for the fixing the bugs!

I guess I will keep you busy more when I test the integrated designer, since as far as i can see, the standalone designer allows static reports only. More on that later on.

Stephano

Reply by email

Michael Van Canneyt
to patspiper
patspiper wrote 19 lines
On 27/02/18 19:04, Michael Van Canneyt via Lazarus wrote: > On Mon, 26 Feb 2018, patspiper via Lazarus wrote: > >> Just to make sure: Once i create report data (SQLDB/firebird) as Data1. I >> cannot set the page or the databand Data property to Data1. Data1 is the >> the OI Data property dropdown, but it will not persist and the entry will >> stay blank. Clicking on the preview icon freezes the designer. >> >> What are be the right steps for data? > > These are the right steps. The data is set. > > The problem is in my misunderstanding how the OI works. For some reason, it > refuses to display component references - even though they are set - if the > component does not include csDesigning in the component state. I fixed > that. I still can't set the Data and ChildBand properties. I updated fpc trunk and lazarus and am testing using the standalone designer.

I will check again tomorrow.

Michael.

Reply by email

patspiper
to Michael Van Canneyt: These are the right steps. The data is set. The problem is in my misunderstanding how the…
Michael Van Canneyt wrote 13 lines
The problem is in my misunderstanding how the OI works. For some reason, it refuses to display component references - even though they are set - if the component does not include csDesigning in the component state. I fixed that. All reported bugs and feature requests except 1 should now be fixed, I also made some other improvements. Make sure you update the FPC repository, some changes to the base classes were needed. Thanks for reporting the bugs !

Any chance of having the following bug fixed today so that i can continue debugging fpReport?

#3306 <https://bugs.freepascal.org/view.php?id=33306> FPReport IDE designer: Data property doesn't list any Data entries, even though they are listed in the right window

Stephano

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20180304/840f9d28/attachment.html>

Reply by email

Michael Van Canneyt
to patspiper
patspiper wrote 20 lines
On 27/02/18 19:04, Michael Van Canneyt via Lazarus wrote: > The problem is in my misunderstanding how the OI works. For some reason, it > refuses to display component references - even though they are set - if the > component does not include csDesigning in the component state. I fixed > that. > > All reported bugs and feature requests except 1 should now be fixed, I also > made some other improvements. > > Make sure you update the FPC repository, some changes to the base classes > were needed. > > Thanks for reporting the bugs ! Any chance of having the following bug fixed today so that i can continue debugging fpReport? #3306 <https://bugs.freepascal.org/view.php?id=33306> FPReport IDE designer: Data property doesn't list any Data entries, even though they are listed in the right window

I will try.

It's not easy because its something that happens in the IDE. So I must be able to reconstruct it outside the IDE.

Michael.

Reply by email

patspiper
to Michael Van Canneyt
Michael Van Canneyt wrote 14 lines
On Sun, 4 Mar 2018, patspiper via Lazarus wrote: > Any chance of having the following bug fixed today so that i can > continue debugging fpReport? > > #3306 <https://bugs.freepascal.org/view.php?id=33306> FPReport IDE > designer: Data property doesn't list any Data entries, even though > they are listed in the right window I will try. It's not easy because its something that happens in the IDE. So I must be able to reconstruct it outside the IDE.

Thanks for fixing it so quickly!

Next in line holding further testing is #3308
<https://bugs.freepascal.org/view.php?id=33308> (FPReport IDE designer: Handling of New/Open/Save proposal)

These 2 bugs are of lower importance than the above, but help make more testing:

#3305 <https://bugs.freepascal.org/view.php?id=33305> FPReport designer: Column headers/footers don't appear in preview when the page's ColumnCount is 1

#3304 <https://bugs.freepascal.org/view.php?id=33304> FPReport designer: HeaderBand and FooterBands properties of DataBand are not persistent

Whenever you have time for them...

Stephano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20180304/e21ec152/attachment.html>

Reply by email