[lazarus] New Bug Entered - lazarus compiled with fpc 1.0.11can\'t open form made with lazarus compiled with 1.9.x

[Vincent Snijders]

On Sat, 27 Dec 2003 20:38:18 +0100
Mattias Gaertner <nc-gaertnma at netcologne.de> wrote:

> On Sat, 27 Dec 2003 17:19:02 +0100  Marc Weustink
> <marc at dommelstein.net> wrote:
> 
> > At 15:47 27-12-2003, Mattias Gaertner wrote:
> > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST)  bugtracker at miraclec.com
> > >wrote:
> > >
> > > >
> > > > Title: lazarus compiled with fpc 1.0.11 can\'t open form made
> > > > with lazarus compiled with 1.9.x
> > > >
> > > > Entered by: Vincent Snijders
> > > >
> > > > I have two lazarus executables lazarus.beta compiled with fpc
> > > > 1.9.1(Compiler Date  : 2003/12/22) and lazarus.release compiled
> > > > with fpc 1.0.11(Compiler Date  : 2003/12/27)/
> > > >
> > > > With lazarus.beta I create a new project with a new form and on
> > > > that form I put a groupbox. I save this project.
> > > >
> > > > If I open this project with lazarus.release I get the message:
> > > > Error while reading Groupbox1.Color : Invalid property value.
> > > > The property value is clBtnFace. Support for reading and writing
> > > > such property values have recently been added to fpc 1.9.
> > > >
> > > > An example in Lazarus: the DebuggerOptionsForm can\'t be opened
> > > > with lazarus.release.
> > >
> > >
> > >Why is this a bug?
> > 
> > I don't know how to call it, but I saw the result of it.
> > 
> > I've still an old FPC (and don't want to spend the time to upgrade
> > it). You have committed a new debugger options form. The moment I
> > read that form, I get a lot of warnings about the color properties,
> > resulting in an allmost empty debugger options dialog.
> > For me this behaviour is a bug and means that I'll suspend
> > development till I found more time to get around this.
> 
> Ok, you can call it a bug.
> 
> As vincent mentioned: We can't do much to "fix" it, because TReader
> reacts correct and the devels want to use the new fpc 1.9.

Maybe this nonsense, but can this ability of the fpc 1.9 reader to read
these property values be backported to fpc 1.0.11?

We already have left (or are leaving) fpc 1.0.10, because of fpImage,
which evolved rather quickly after the release of fpc 1.0.10.

Vincent.