On 05/09/2013 21:03, Martin wrote:
On 05/09/2013 20:57, Junior wrote:
Open project test.
In Object Inspector, click in tabsheet1, tabsheet2, ...
all components that are within tabsheets disappear.
Ok, confirmed.
It seems to be design time only?
When I run the project, they are all there?
On 05.09.2013 15:13, Antonio Fortuny wrote:
The usual work flow is like this:
You alter fpc units and tests them with some test program (ppu files in
source\packages\fcl-db\units\...).
OK
When you are done, you build all fpc packages that depend on these
ppus and copy
all new files to the ins
On 05/09/2013 19:55, Junior wrote:
I mean that all components that are within tabsheets disappear.
sorry, need more details, all works fine here.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/ma
I mean that all components that are within tabsheets disappear.
Em 05-09-2013 15:43, Martin escreveu:
On 05/09/2013 19:19, Junior wrote:
Lazarus 1.1 r42622M FPC 2.6.2 i386-linux-gtk 2
The property ShowTabs of the component PageControl not drawing the
screen in the Lazarus IDE.
The error occ
On 05/09/2013 19:19, Junior wrote:
Lazarus 1.1 r42622M FPC 2.6.2 i386-linux-gtk 2
The property ShowTabs of the component PageControl not drawing the
screen in the Lazarus IDE.
The error occurs when it adds more than one page.
1 PageControl (add 2 tabsheet);
Add um button into tabsheet;
click
Lazarus 1.1 r42622M FPC 2.6.2 i386-linux-gtk 2
The property ShowTabs of the component PageControl not drawing the
screen in the Lazarus IDE.
The error occurs when it adds more than one page.
1 PageControl (add 2 tabsheet);
Add um button into tabsheet;
click on tabsheet navigating on them.
th
Le 05/09/2013 15:50, Reinier Olislagers
a écrit :
It's still a little bit too early to acomplish this step. But anyway
I'll be glad to do it when I'm satisfied with the additions, including
unit tests and some help text.
OK - just to cl
On 05/09/2013 15:33, Antonio Fortuny wrote:
>> You can use the FPC database test suite for that (e.g.
>> dbtestframework_gui), see e.g.
>> http://wiki.lazarus.freepascal.org/Databases#Running_FPC_database_tests
>>
>> You can add new unit tests to e.g. testspecifictbufdataset.pas
> It's still a li
You can use the FPC database test suite for that (e.g.
dbtestframework_gui), see e.g.
http://wiki.lazarus.freepascal.org/Databases#Running_FPC_database_tests
You can add new unit tests to e.g. testspecifictbufdataset.pas
When you are done, you build all fpc packa
On 05/09/2013 14:34, Mattias Gaertner wrote:
>> Antonio Fortuny hat am 5. September 2013 um 13:58
>> geschrieben:
>> I want to make some changes and additions to the unit bufdataset.pas
>> incresing dataset possibilities.
>> I've made the changes, compiled and tested using a dynamically creat
The usual work flow is like this:
You alter fpc units and tests them with some test program (ppu files in
source\packages\fcl-db\units\...).
OK
When you are done, you build all fpc packages that depend on these ppus and copy
all new files to the install folders (fpc\2.6.2\units\...).
Done with
> Antonio Fortuny hat am 5. September 2013 um 13:58
> geschrieben:
>
> Hi Folks.
>
> I want to make some changes and additions to the unit bufdataset.pas
>incresing dataset possibilities.
> I've made the changes, compiled and tested using a dynamically created
>component.
> So far, so good
Hi Folks.
I want to make some changes and additions to the unit bufdataset.pas
incresing dataset possibilities.
I've made the changes, compiled and tested using a dynamically created
component.
So far, so good.
Now I want to incorporate the changes in the FCL package fcl-db
Vista32, Lazarus 1.
13 matches
Mail list logo
