On 07/05/18 17:54, Gabor Boros via Lazarus wrote:
My main development toolset is FPC 3.0.4 and Lazarus fixes_1_8.
Sometimes I try some things with Lazarus trunk also. It is easy.
But now build up a new development machine from scratch with RHEL 7.5
on it and try to utilize FPC trunk too (with
On 07/05/18 17:54, Gabor Boros via Lazarus wrote:
My main development toolset is FPC 3.0.4 and Lazarus fixes_1_8.
Sometimes I try some things with Lazarus trunk also. It is easy.
But now build up a new development machine from scratch with RHEL 7.5
on it and try to utilize FPC trunk too (with
(such as fpc debug units) have not
been implemented yet, but the basic features work like a charm.
Stephano
Am 11.05.18 um 15:40 schrieb patspiper via Lazarus:
On 11/05/18 16:17, Joost van der Sluis via Lazarus wrote:
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot is work
On 12/05/18 23:55, Jesus Reyes A. via Lazarus wrote:
En Fri, 11 May 2018 08:40:28 -0500, patspiper via Lazarus
<lazarus@lists.lazarus-ide.org> escribió:
On 11/05/18 16:17, Joost van der Sluis via Lazarus wrote:
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot i
On 11/05/18 16:17, Joost van der Sluis via Lazarus wrote:
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot is work in progress
Sorry, but I don't think this is an improvement. For new users this
looks like a nightmare. It should be hidden, at least, imho. Or
better
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
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
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
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
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
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
TFPRreport and TFPJSONReport need some clarifications. Maybe MVC can
confirm/correct the below:
TFPRreport:
- Report design can be setup by code *only*.
- TFPReportData components must be linked to TFRReport by code
- Can invoke the IDE integrated editor to design reports and open/save
them
12 matches
Mail list logo
