On Sun, 4 Mar 2018, patspiper via Lazarus wrote:
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
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
On Tue, 27 Feb 2018, patspiper wrote:
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
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
On Mon, 26 Feb 2018, patspiper via Lazarus wrote:
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
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
The second bug is in the standalone-designer too.
Andreas
Am 26.02.2018 um 19:03 schrieb Andreas Frieß via Lazarus:
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
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
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
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.
On Mon, 26 Feb 2018, Andreas Frieß via Lazarus wrote:
Actual it make IMHO only sense with the
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
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
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
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
14 matches
Mail list logo
