> Could someone out there please fix these issues and send
> the changes to me for inclusion in the next sub-release?

<...>

> > a) the "model" sub property let you choose (at design time)
> > the same control (itself), hanging Dephi (crash!)

This ones easy I have fix ready for this.

> > b) the "model" sub property can be circular, i.e. Control1
> > has Control2 as model, while Control2 has Control1. No
> > problem at design time, I don't know at runtime.

Actually it can cause problems at designtime. Delphi5 quietly quit on
me when I set this up - no message or anything, just that suddenly
Delphi was not there any more.

Fixing this is more difficult, because there is no common base to all
the different components that use AutoLabel. What I propose to do is
prevent assigning the model property of a component that is already
being used as a model. This is not perfect...

You could assign the model property of ControlA to ControlB. Then you
can assign the model property of ControlC to ControlA. Hence ControlA
gets both a model property assignment and is used as a model itself.
However the references are still not circular, and it will remain
impossible to assign the model property of ControlB to any other
control - because ControlB already has a model reference from
ControlA. (Clear as mud ;-)

So the questions are...

1. Does this sound acceptable (am I missing anything in my logic)?

2. Should the rejection of a model assignment result in a message, or
do I simply ignore the attempt?

> > c) I want to increase the space between the end of the label

I explained how to do this. Perhaps there are still some issues in
regard to property names or property availability but I dont want to
tackle those right now.


Geoff Worboys
Telesis Computing