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

[Mattias Gaertner]

On Sat, 27 Dec 2003 23:06:51 +0100  Marc Weustink <marc at dommelstein.net>
wrote:

> At 21:00 27-12-2003, Mattias Gaertner wrote:
> >On Sat, 27 Dec 2003 20:47:56 +0100  Marc Weustink <marc at dommelstein.net>
> >wrote:
> >
> > > At 20:38 27-12-2003, Mattias Gaertner 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.
> > >
> > > Ah, I didn't realize that it had something to do with Treader
> > >
> > > >What we can do, is to set all colors and charsets to their default
> > > >values. To make things a little easier, I implemented default values
> > > >for property editors and object inspector.
> > > >In the popupmenu of the OI there is a new menu item to set the
> > > >default value.
> > > >
> > > >Now, we have to set default values for all lcl controls to the right
> > > >value, so that the colors and charsets are no longer saved to the
> > > >form streams.
> > >
> > > Ehm, can't we set for the time beeing the stored flag to False for
> > > those types of properties which have a problem with older versions ?
> >
> >If we search for all props and add Stored functions, or if we set the
> >correct default value: We have to open all lfm files and fix the lrs
> >files anyway. Workaround and fix will be a similar amount of work.
> 
> It is a lot of work in both cases. However when you don't store the props 
> by  defining a directive (or so), you avoid that a property is accidently 
> changed from default would cause problems.

You can always break code by accident. ;)

But in this case we are talking about colors and charsets. The IDE units
don't use them.


Mattias