Sign in Join

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

Mailing lists / lazarus / 2003-12

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

21 messages · 5 people ·

Reply by email Subscribe to this list Your subscription

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

Mattias Gaertner
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 20 lines
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?

Mattias

Reply by email

Ken Moffat
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Vincent Snijders wrote 8 lines
... this project needs fpc 1.9 to compile and you shouldn't expect backward compatibility. If that is your response, than lazarus from now on needs fpc 1.9.x to compile. You can compile lazarus with fpc 1.0 without problem, but you can't open the debugger options dialog.

I have lazarus from cvs and fpc 1.0.11, and I can open the debugger options dialog.

(he then sticks his tongue out for emphasis) :-)

Ken is kidding, sorry

Reply by email

Mattias Gaertner
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 60 lines
At 20:38 27-12-2003, Mattias Gaertner wrote: >On Sat, 27 Dec 2003 17:19:02 +0100 Marc Weustink >wrote: > > > At 15:47 27-12-2003, Mattias Gaertner wrote: > > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) > > >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.

Mattias

Reply by email

Mattias Gaertner
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 35 lines
At 15:47 27-12-2003, Mattias Gaertner wrote: >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) 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.

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.

Mattias

Reply by email

Marc Weustink
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Mattias Gaertner wrote 43 lines
On Sat, 27 Dec 2003 17:19:02 +0100 Marc Weustink wrote: > At 15:47 27-12-2003, Mattias Gaertner wrote: > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) 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

Show quoted text 8 lines
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 ?

Marc

Reply by email

Marc Weustink
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Mattias Gaertner wrote 25 lines
On Sat, 27 Dec 2003 09:40:25 -0500 (EST) 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.

Marc

Show quoted text 6 lines
Mattias _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives

Reply by email

Unknown author

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.

Reply by email

Vincent Snijders
to Unknown author
Show quoted text 44 lines
On Sat, 27 Dec 2003 17:19:02 +0100 Marc Weustink wrote: > At 15:47 27-12-2003, Mattias Gaertner wrote: > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) > >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.

Reply by email

Marc Weustink
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Ken Moffat wrote 12 lines
Vincent Snijders wrote: >... this project needs fpc 1.9 >to compile and you shouldn't expect backward compatibility. If that is >your response, than lazarus from now on needs fpc 1.9.x to compile. You >can compile lazarus with fpc 1.0 without problem, but you can't open the >debugger options dialog. > > I have lazarus from cvs and fpc 1.0.11, and I can open the debugger options dialog.

And you still see tabpages controls etc ?

Marc

Reply by email

Vincent Snijders
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 28 lines
On Sat, 27 Dec 2003 09:40:25 -0500 (EST) 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? Mattias

Good questtion. I am not sure it is a bug, though IMO it is an unwanted feature, that lazarus compiled with fpc 1.9 save forms in a format, that can't be opened (shown) without errors, when compiled with fpc 1.0.

For the test project above you could say that this project needs fpc 1.9 to compile and you shouldn't expect backward compatibility. If that is your response, than lazarus from now on needs fpc 1.9.x to compile. You can compile lazarus with fpc 1.0 without problem, but you can't open the debugger options dialog.

If I want to be able to use the debugger options dialog, I must use lazarus compiled with fpc 1.9. In that case can't use fpc 1.0.x to compile projects, because of Invalid property values. IMO compiling with fpc 1.0.x is still needed, because fpc 1.9 is still beta and the only fpc 1.9.x, which can be downloaded as installable package, is fpc 1.9.0, which has at least one show stopper bug with respect to lazarus. (Can't create pipe; linuxerror).

Vincent.

Reply by email

Vincent Snijders
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 21 lines
Vincent Snijders wrote: >... this project needs fpc 1.9 >to compile and you shouldn't expect backward compatibility. If that >is your response, than lazarus from now on needs fpc 1.9.x to >compile. You can compile lazarus with fpc 1.0 without problem, but >you can't open the debugger options dialog. > > > I have lazarus from cvs and fpc 1.0.11, and I can open the debugger options dialog. (he then sticks his tongue out for emphasis) :-) -- Ken is kidding, sorry

What date is your lazarus binary?

Vincent.

Reply by email

Marc Weustink
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Ken Moffat wrote 14 lines
Marc Weustink wrote: >> >>I have lazarus from cvs and fpc 1.0.11, and I can open the debugger >>options dialog. > > >And you still see tabpages controls etc ? > > > Yes. Looks functional. Haven't actually used it except to just navigate around the various pages.

Also if you open the Debuggeroptions dialog itself as form in Lazarus ?

Marc

Reply by email

Mattias Gaertner
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 50 lines
On Sat, 27 Dec 2003 20:38:18 +0100 Mattias Gaertner wrote: > On Sat, 27 Dec 2003 17:19:02 +0100 Marc Weustink > wrote: > > > At 15:47 27-12-2003, Mattias Gaertner wrote: > > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) > > >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?

yes.

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.

Mattias

Reply by email

Marc Weustink
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Ken Moffat wrote 11 lines
Marc Weustink wrote: >> >>Yes. Looks functional. Haven't actually used it except to just navigate >>around the various pages. > > >Also if you open the Debuggeroptions dialog itself as form in Lazarus ? Yes, looks ok. used the open icon to open DebugOptionsFrm.pas. Seems to be fine. Maybe 1.0.11 is the answer? Are you on 1.0.10?

OK, , but vincent (who reported the original message) was on 1.0.11

Il'' try 1.0.11 tomorrow to see if it helps

Marc

Show quoted text 9 lines
-- Ken _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives

Reply by email

Marc Weustink
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Mattias Gaertner wrote 67 lines
On Sat, 27 Dec 2003 20:47:56 +0100 Marc Weustink wrote: > At 20:38 27-12-2003, Mattias Gaertner wrote: > >On Sat, 27 Dec 2003 17:19:02 +0100 Marc Weustink > >wrote: > > > > > At 15:47 27-12-2003, Mattias Gaertner wrote: > > > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) > > > >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.

Marc

Reply by email

Vincent Snijders
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 16 lines
Vincent Snijders wrote: > >What date is your lazarus binary? > >Vincent. > > > > lazarus 15048420 Dec 26 22:05 /usr/share/lazarus/lazarus built from cvs source. -- Ken

I think you just got lucky.

The problem was inserted in cvs at Fri Dec 26 15:29:33 2003 UTC, so assuming local time in your message, about one hour after you updated from cvs.

And because Mattias fixed it so quickly, you will never notice this problem with the debugger options dialog.

If you want to have a more complete experience with lazarus (including all the problems mentioned on the list), you have to update from cvs more often. ;-)

(he then sticks his tongue out for emphasis) :-)

Vincent is kidding too.

Reply by email

Ken Moffat
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Vincent Snijders wrote 8 lines
If you want to have a more complete experience with lazarus (including all the problems mentioned on the list), you have to update from cvs more often. ;-) (he then sticks his tongue out for emphasis) :-)

:-)

I'm finding this problem has now bitten me. Having taken your advice and updated ;-) , lazarus now crashes with an access violation when I try to access the debugger options dialog. Arghh, matey!

Ken

Reply by email

Mattias Gaertner
to Unknown author: Title: lazarus compiled with fpc 1.0.11 can\'t open form made with lazarus compiled with…
Show quoted text 73 lines
At 21:00 27-12-2003, Mattias Gaertner wrote: >On Sat, 27 Dec 2003 20:47:56 +0100 Marc Weustink >wrote: > > > At 20:38 27-12-2003, Mattias Gaertner wrote: > > >On Sat, 27 Dec 2003 17:19:02 +0100 Marc Weustink > > > wrote: > > > > > > > At 15:47 27-12-2003, Mattias Gaertner wrote: > > > > >On Sat, 27 Dec 2003 09:40:25 -0500 (EST) > > > > >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

Reply by email