Sign in Join

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

Mailing lists / lazarus / 2008-02

TextHeight property in TCustomForm

10 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

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

Hess, Philip J
to Mattias Gaertner

Removing TextHeight broke:

- All Orpheus property editors.
- All Orpheus test apps whose forms were converted from Delphi.
- All of my own apps whose forms were converted from Delphi.

Was this really necessary?

Thanks.

-Phil

Earlier message 22 lines
-----Original Message----- From: [mailto:] On Behalf Of Mattias Gaertner Sent: Tuesday, February 19, 2008 2:04 PM To: Subject: Re: [Lazarus] TextHeight property in TCustomForm On Tue, 19 Feb 2008 10:41:17 +0200 "zaher dirkey" wrote: > TCustomForm class > > property TextHeight: Longint read FDummyTextHeight write > FDummyTextHeight > stored False; > For What? I removed it. Mattias

Reply by email

Vincent Snijders
to Hess, Philip J
Philip J wrote 9 lines
Removing TextHeight broke: - All Orpheus property editors. - All Orpheus test apps whose forms were converted from Delphi. - All of my own apps whose forms were converted from Delphi. Was this really necessary? Thanks.

Maybe it should never have been in a .lfm in the first place and the conversion was wrong.

Vincent

Reply by email

Hess, Philip J
to Vincent Snijders

But did removing it add any value to Lazarus?

All I know is that what once worked no longer does.

TextHeight is probably a holdover from early versions of Delphi, but Delphi still puts TextHeight in the .dfm. So if you want better compatibility...

Thanks.

-Phil

Earlier message 23 lines
-----Original Message----- From: [mailto:] On Behalf Of Vincent Snijders Sent: Wednesday, February 27, 2008 4:45 PM To: General mailing list Subject: Re: [Lazarus] TextHeight property in TCustomForm Hess, Philip J schreef: > Removing TextHeight broke: > > - All Orpheus property editors. > - All Orpheus test apps whose forms were converted from Delphi. > - All of my own apps whose forms were converted from Delphi. > > Was this really necessary? > > Thanks. Maybe it should never have been in a .lfm in the first place and the conversion was wrong. Vincent

Reply by email

Vincent Snijders
to Hess, Philip J
Philip J wrote
But did removing it add any value to Lazarus?

Any value? Yes. Less confusion about unused properties.

How much value, maybe very little.

Show quoted text 7 lines
All I know is that what once worked no longer does. TextHeight is probably a holdover from early versions of Delphi, but Delphi still puts TextHeight in the .dfm. So if you want better compatibility...

Me personally, no I don't want compatibility with unused Delphi ballast.

Vincent

Reply by email

Hess, Philip J
to Vincent Snijders

Vincent,

I'm not sure if you appreciate the hassle this teeny, tiny change has caused. Now anyone who ever installed the ported Orpheus package, when they move to a newer Lazarus will discover that it no longer works. Period.

The fix is not difficult but I can't retroactively upgrade others' installations.

This is my main issue with Lazarus these days: How perfectly good code slowly "erodes" over time as Lazarus advances. It's almost impossible to keep up. Staying with a stable build is not an option since the widgetset improvements we need are often tied to LCL changes as well.

Thanks.

-Phil

Earlier message 26 lines
-----Original Message----- From: [mailto:] On Behalf Of Vincent Snijders Sent: Wednesday, February 27, 2008 5:14 PM To: General mailing list Subject: Re: [Lazarus] TextHeight property in TCustomForm Hess, Philip J schreef: > But did removing it add any value to Lazarus? Any value? Yes. Less confusion about unused properties. How much value, maybe very little. > > All I know is that what once worked no longer does. > > TextHeight is probably a holdover from early versions of Delphi, but > Delphi still puts TextHeight in the .dfm. So if you want better > compatibility... > Me personally, no I don't want compatibility with unused Delphi ballast. Vincent

Reply by email

Flávio Etrusco
to Hess, Philip J: But did removing it add any value to Lazarus? All I know is that what once worked no…
Philip J wrote 13 lines
But did removing it add any value to Lazarus? All I know is that what once worked no longer does. TextHeight is probably a holdover from early versions of Delphi, but Delphi still puts TextHeight in the .dfm. So if you want better compatibility... Thanks. -Phil

My 2cents suggestions if the property is restored:
- use a dummy method instead of a field/variable? (mostly for the code cleanliness rather than the wastage of heap memory)
- would it work to make it write-only so it's not displayed in the Object Inpector?

Cheers,
Fl?vio

Reply by email

Mattias Gaertner
to Hess, Philip J: But did removing it add any value to Lazarus? All I know is that what once worked no…
Philip J" wrote 7 lines
But did removing it add any value to Lazarus? All I know is that what once worked no longer does. TextHeight is probably a holdover from early versions of Delphi, but Delphi still puts TextHeight in the .dfm. So if you want better compatibility...

Sorry for the trouble, but there is hope.
Today I added LCLVersion to forms.
Now we can start writing an automatic lfm converter/clean up for the IDE.

Mattias

Reply by email

Mattias Gaertner
to Hess, Philip J: I'm not sure if you appreciate the hassle this teeny, tiny change has caused. Now anyone…
Philip J" wrote 6 lines
Vincent, I'm not sure if you appreciate the hassle this teeny, tiny change has caused. Now anyone who ever installed the ported Orpheus package, when they move to a newer Lazarus will discover that it no longer works. Period.

It's a pity that Borland didn't think about versioning when they created TReader/TWriter.

Show quoted text 7 lines
The fix is not difficult but I can't retroactively upgrade others' installations. This is my main issue with Lazarus these days: How perfectly good code slowly "erodes" over time as Lazarus advances. It's almost impossible to keep up. Staying with a stable build is not an option since the widgetset improvements we need are often tied to LCL changes as well.

That's why we need a tool for that.

Mattias

Reply by email