Hmm, Lazarus site should be adapted for the 1.0.10 release?

( :-) )

I thought, I fixed this bug last friday. It still works for me.

Mattias

Renaming a datamodule is also puzzling. Instead of updating the DM's class and form variable name, the IDE generates the following code: [...]

Fixed.

Mattias

After a fresh CVS build there still seem to be some issues with TDatamodule. Bringing up Lazarus into a new project and then adding a new datamodule from the file|new menu blanks out most of the components in the palette when the DM form appears. I thought it might be something odd with my workstation so I did a fresh cvs checkout and build on new machine with the same results.

Renaming a datamodule is also puzzling. Instead of updating the DM's class and form variable name, the IDE generates the following code:

type
  TDataModule2 = class(TDataModule)
    NewDMName: TDataModule2;
  private
    { private declarations }
  public
    { public declarations }
  end;
var
  DataModule2: TDataModule2;

-Tom

Thanks Mattias.

One additional thing I noticed is double clicking on the TDatamodule form throws an exception: TComponentInterface.GetDesigner.DataModule1 Owner=Nil. I don't know if everything is implemented with datamodules yet but I thought I'd let you know.

-Tom

Title: DataModule doubleclick

Entered by: Dominik Zablotny

Original Description:
Accidental doubleclick on datamodule view (designer) gives a message
"TComponentInterface.GetDesigner DataModule1 Owner = nil" I'ts annoing because "cancel" makes lazarus halt.

Updated by: Mattias

Status: Fixed

Comments:
MG

Title: bug in TRadiogroup

Entered by: mapelo

Original Description:
if you create a Radiogroup1 into a form, then
Radiogroup1.Items.Add('anything');

does not work (no error, but no insert item)

Updated by: Mattias

Status: Fixed

Comments:
MG

El Viernes, 11 de Julio de 2003 14:18, Michael Van Canneyt escribi�:

SSSSSSSSSSSSSSShhhhh!!!!!!

Borland is looking for good programmers like Mattias. Thanks Mattias and other people for your proyect Lazarus.

---

Saludos
Manuel P�rez L�pez

Borland is going to have a hard time beating the bugreport-bugfix response time of Lazarus ;-)

Michael.

If there's a release coming up, I think a better priority would be an installer that installs both Lazaurus and FPC.

Title: .lpi is not a historic file

Entered by: mapelo

Original Description:
freepascal pre1.08
Linux

Description:

1- Create a new proyect (application).
2- Create two units called, for example, unit1 (for form1) and unit2 (no form). 3.- Save de proyect (call it proyect1) and exit.

Now, open Lazarus and Load the proyect1:
1.- Remove from proyect (Proyect->Remove form proyect) the unit2.pas 2.- Close the unit2 from Lazarus Editor
2.- Save the proyect1.

The bug: you can see into proyect1.lpi, because Lazarus do not delete the reference for the unit2. There is no problem, because the proyect run OK, but if you are programing a big application, the .lpi shows all the unit you deleted. The .lpi is a historic file????

Updated by: Mattias

Status: Not a bug

Comments:
the .lpi file also stores session information.
You can deactivate it for the current project in Project -> Project Options -> Info.

> One additional thing I noticed is double clicking on the TDatamodule > form throws an exception:... I thought, I fixed this bug last friday. It still works for me.

Oops... it's probably ok. Everything has been working so well that I haven't done an cvs update since early last week. Guess now would probably be a good time!

-Tom

Title: TDatamodule OnCreate never fires

Entered by: Tom Lisjac

Original Description:

Updated by: Mattias

Status: Fixed

Comments:
MG

Title: TCalendar crashes at start

Entered by: Doiminik Zablotny

Original Description:
When I put calendar on the form and run the program it immediatly crashes (doesn't even show),
at design time it looks OK.
I have Polish locale set in GTK.

Updated by: Mattias

Status: Unreproducable

Comments:
MG

This is normal: Only components that can be used on a TDatamodule will be shown. (Same happens in D6/7/Kylix3) You need for instance to have the TIBQuery packages installed to see something.

That's a nice feature! I stopped upgrading at D5 and K2 so I'd never seen this behavior before! :)

Thanks,

-Tom

This is normal: Only components that can be used on a TDatamodule will be shown. (Same happens in D6/7/Kylix3) You need for instance to have the TIBQuery packages installed to see something.

Michael.

Title: Foward class reference disables RTTI in property editor

Entered by: Tom Lisjac

Original Description:
Declaring a forward class reference for a component masks access to it in the property editor after it is installed. The component runs fine if manually initialized at runtime but the property editor is completely blank when viewing it in the IDE at design time. An example is attached that reproduces the problem.

A workaround that restores design time access is to remove the forward reference, declare generic pointers and typecast them where needed.

unit fwdtest;
interface
uses
  SysUtils, Classes, Graphics, Controls, Forms, Dialogs;
type
  TMain = class;
  TMainXprops = class(TPersistent)
  private
    fParent:TMain;
    finteger:integer;
    fString: String;
  published
    property Parent :TMain read fParent write fParent;
    property AnInteger:Integer read finteger write finteger;
    property AString:String read fString write fString;
  end;
  TMain = class(TComponent)
  private
    fy:TMainXProps;
  Public
    Constructor Create(AOwner:TComponent); Override;
    Destructor Destroy; Override;
  published
    property testprop:TMainXProps read fy write fy;
  end;
procedure Register;
implementation
procedure Register;
begin
  RegisterComponents('Misc', [TMain]);
end;

{ TMain }

constructor TMain.Create(AOwner: TComponent);
begin
  inherited;
  fy:=TMainXProps.Create;
end;
destructor TMain.Destroy;
begin
  fy.free;
  inherited;
end;
end.

Updated by: Mattias

Status: Not a bug

Comments:
This is not a lazarus bug, but the FPC bug 2492.

Title: Foward class reference disables RTTI in property editor

Entered by: Tom Lisjac

Original Description:
Declaring a forward class reference for a component masks access to it in the property editor after it is installed. The component runs fine if manually initialized at runtime but the property editor is completely blank when viewing it in the IDE at design time. An example is attached that reproduces the problem.

A workaround that restores design time access is to remove the forward reference, declare generic pointers and typecast them where needed.

unit fwdtest;
interface
uses
  SysUtils, Classes, Graphics, Controls, Forms, Dialogs;
type
  TMain = class;
  TMainXprops = class(TPersistent)
  private
    fParent:TMain;
    finteger:integer;
    fString: String;
  published
    property Parent :TMain read fParent write fParent;
    property AnInteger:Integer read finteger write finteger;
    property AString:String read fString write fString;
  end;
  TMain = class(TComponent)
  private
    fy:TMainXProps;
  Public
    Constructor Create(AOwner:TComponent); Override;
    Destructor Destroy; Override;
  published
    property testprop:TMainXProps read fy write fy;
  end;
procedure Register;
implementation
procedure Register;
begin
  RegisterComponents('Misc', [TMain]);
end;

{ TMain }

constructor TMain.Create(AOwner: TComponent);
begin
  inherited;
  fy:=TMainXProps.Create;
end;
destructor TMain.Destroy;
begin
  fy.free;
  inherited;
end;
end.

Updated by: Mattias

Status: Not a bug

Comments:
This is not a lazarus bug, but the FPC bug 2429.

But this bug is fixed, according to the fpc bugtracker.

in

the property editor after it is installed. The component runs fine if manually initialized at runtime but the property editor is completely blank when viewing it in the IDE at design time. An example is

attached

I know, they wanted to hire me too when they started Kylix. If I see what they do (or better, don't do) I'm glad I didn't take the offer...

Thanks Mattias and other people for your proyect Lazarus.

When the 1.2 FPC compiler comes out, we'll have plenty of more platforms to run Lazarus on :-)

Michael.

Title: Datamodule generates AV on Lazarus exit

Entered by: Tom Lisjac

Original Description:
When a datamodule is renamed, OldCreateOrder is set and OnCreate and OnDestroy events exist, Lazarus will AV upon exit with 1.0.10. Here are the steps to reproduce:

Bring up Lazarus in a new project.
Add a datamodule with File | New | Datamodule
With Property editor:
Rename the datamodule to dmt
Set OldCreationOrder to True
Create empty OnCreate and OnDestroy event handlers Exiting Lazarus (saving or not) generates an AV

This problem appeared after upgrading to 1.0.10 in a datamodule that had been working fine with 1.0.7.

Updated by: Mattias

Status: Fixed

Comments:
I added a workaround in TDatamodule for this bug. The real bug ill be fixed with a new TReader/TWriter.

Title: There is no TPageControl, TTabSheet

Entered by: tom

Original Description:
{$IFNDEF FPC}
PageControl1: TPageControl;
TabSheet1: TTabSheet;
{$ENDIF}

Updated by: Mattias

Status: Not a bug

Comments:
Moved to the ToDo list "Roadmap"

Title: const clCream is missing

Entered by: Peter

Original Description:

clCream = TColor($00F0FBFF);

is new since D7

Updated by: Mattias

Status: Fixed

Comments:
MG

Title: There is no SizeGrip property in TStatusbar

Entered by: tom

Original Description:
{$IFNDEF FPC}
  StatusBar1.SizeGrip := true;
{$ENDIF}

Updated by: Mattias

Status: Not a bug

Comments:
Moved to the ToDo list "Roadmap"
MG

Title: There is no Tracking property in TScrollbox

Entered by: tom

Original Description:
{$IFNDEF FPC}
  ScrollBox1.HorzScrollBar.Tracking:=true;
{$ENDIF}

Updated by: Mattias

Status: Not a bug

Comments:
I moved this to the ToDo list "Roadmap"

MG

Title: There is no AutoComplete property in TComboBox

Entered by: tom

Original Description:
{$IFNDEF FPC}
ComboBox1.AutoComplete := false;
{$ENDIF}

Updated by: Mattias

Status: Not a bug

Comments:
Moved to the ToDo list "Roadmap"
MG

Title: Update procedure from TForm is missing

Entered by: tom

Original Description:
{$IFNDEF FPC}
  Form.Update;
{$ENDIF}

Updated by: Mattias

Status: Not a bug

Comments:
Moved to the ToDo list "Roadmap"

MG

Title: There is no Action property in TToolButton

Entered by: tom

Original Description:
{$IFNDEF FPC}
  ToolButton1.Action := actMyAction;
{$ENDIF}
property Action: TBasicAction;

Updated by: Mattias

Status: Not a bug

Comments:
Moved to the ToDo list "Roadmap"

MG