Subject | Re: [IBO] IBO treeview |
---|---|
Author | Paul Gallagher |
Post date | 2001-01-28T15:15:54Z |
Im confused. In the ComboBoxEnh component, the DisplayField property is
defined, and published as a simple string property, yet in the object
inspector, it shows up as a datafield property with the dropdown. I don't
see how it gets there.
Paul
defined, and published as a simple string property, yet in the object
inspector, it shows up as a datafield property with the dropdown. I don't
see how it gets there.
Paul
----- Original Message -----
From: "Paul Gallagher" <paul@...>
To: <IBObjects@yahoogroups.com>
Sent: Sunday, January 28, 2001 8:59 AM
Subject: Re: [IBO] IBO treeview
> Thanks Geoff.
>
> I will study your code for the ComboBoxEnh component. It appears to be
what
> I am trying to do. I'm surprised how much interest this project has
> generated. Seems like there is a need for a component like this. I hope I
> don't disappoint anyone.
>
> Paul
>
> ----- Original Message -----
> From: "Geoff Worboys" <geoff@...>
> To: <IBObjects@yahoogroups.com>
> Sent: Sunday, January 28, 2001 2:11 AM
> Subject: Re: [IBO] IBO treeview
>
>
> > > This is going to be tough. Im thinking about creating
> > > subclasses for FieldDataLink, and calling them
> > > ParentFieldDataLink, KeyFieldDataLink, DisplayFieldDataLink,
> > > etc... Looks like there will be 4-5 different fields
> > > required for this component.
> > >
> > > Any thoughts?
> >
> > Use TIB_InterfaceDataLink and set the Control property to the
> > treeview. This is simply a derivation of TIB_DataLink - no specific
> > field support. The add string fields to store each of the field names
> > during design/unprepared stages. When prepared obtain the column
> > references and assign them to internal TIB_Column properties for
> > faster access.
> >
> > In some of my CustomEditEnh derivations I use a FieldDataLink, then
> > simply a fieldname for the one extra field (DisplayField) that I use
> > in things like ComboBox. I use that for FieldByName lookups, but for
> > better optimisation I should probably do what I describe above.
> >
> > In LookupEnh I use two separate datalinks, but that is because I am
> > linking to two different datasets. You will find it much simpler to
> > have only a single datalink per dataset that you need to reference
> > (IMO).
> >
> > My thoughts.
> >
> > Geoff Worboys
> > Telesis Computing
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>