Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Micha Nelissen wrote:
Michael
On Wed, 20 Jun 2007, Marc Weustink wrote:
> Michael Van Canneyt wrote:
> >
> > On Wed, 20 Jun 2007, Marc Weustink wrote:
> >
> > > Michael Van Canneyt wrote:
> > > > On Wed, 20 Jun 2007, Marc Weustink wrote:
> > > >
> > > > > Michael Van Canneyt wrote:
> > > > > > On Wed, 20 Jun 2007, Micha Ne
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Micha Nelissen wrote:
Michael Van Canneyt wrote:
This is due to a Delphi compatibility fix. Component
On Wed, 20 Jun 2007, Marc Weustink wrote:
> Michael Van Canneyt wrote:
> >
> > On Wed, 20 Jun 2007, Marc Weustink wrote:
> >
> > > Michael Van Canneyt wrote:
> > > > On Wed, 20 Jun 2007, Micha Nelissen wrote:
> > > >
> > > > > Michael Van Canneyt wrote:
> > > > > > This is due to a Delphi comp
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Micha Nelissen wrote:
Michael Van Canneyt wrote:
This is due to a Delphi compatibility fix. Component names must be valid
identifiers. Logical, since the name must match the
On Wed, 20 Jun 2007, Marc Weustink wrote:
> Michael Van Canneyt wrote:
> >
> > On Wed, 20 Jun 2007, Micha Nelissen wrote:
> >
> > > Michael Van Canneyt wrote:
> > > > This is due to a Delphi compatibility fix. Component names must be valid
> > > > identifiers. Logical, since the name must matc
Michael Van Canneyt wrote:
On Wed, 20 Jun 2007, Micha Nelissen wrote:
Michael Van Canneyt wrote:
This is due to a Delphi compatibility fix. Component names must be valid
identifiers. Logical, since the name must match the field name in the form,
Why *must* it match a field name in the form ?
On Wed, 20 Jun 2007, Micha Nelissen wrote:
> Michael Van Canneyt wrote:
> > This is due to a Delphi compatibility fix. Component names must be valid
> > identifiers. Logical, since the name must match the field name in the form,
>
> Why *must* it match a field name in the form ?
Because the st
Michael Van Canneyt wrote:
This is due to a Delphi compatibility fix. Component names must be valid
identifiers. Logical, since the name must match the field name in the form,
Why *must* it match a field name in the form ?
Micha
___
fpc-devel maillis
On Wed, 20 Jun 2007, Graeme Geldenhuys wrote:
> The other thing I noticed as well is that you can't use the hash (#)
> character in the component name anymore.
>
> I used to name all internal components in fpGUI as '#button' or
> '#edit'. I had to change all of them to '_button' or '_edit'. N
On Wed, 20 Jun 2007, Martin Schreiber wrote:
> Hi,
> A possible show stopper for FPC 2.2:
>
> http://www.freepascal.org/mantis/view.php?id=9115
Fixed and merged.
Michael.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepas
The other thing I noticed as well is that you can't use the hash (#)
character in the component name anymore.
I used to name all internal components in fpGUI as '#button' or
'#edit'. I had to change all of them to '_button' or '_edit'. Not a
show stopper though.
Graeme.
On 20/06/07, Martin S
Hi,
A possible show stopper for FPC 2.2:
http://www.freepascal.org/mantis/view.php?id=9115
Martin
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
13 matches
Mail list logo
