Author: Duncan Parsons
Some properties of a component can 'drop-down' to reveal other properties (such as
a Font property reveals various properties within itself). These are objects within
the component, and a simple demonstration of how to add you own new 'drop-down'
properties is given here. (You can also get a Static Analogue Clock Component
too!!!)
Answer:
Please Note: I will only include here pertinent aspects of what is being explained.
I will not flesh out all the examples for the sake of clarity.
To include an object within a component is a fairly simple matter, simply declare a
field, and make a property public.
1 interface
2
3 type
4 TMyComp = class(TComponent)
5 private
6 fFont: TFont;
7 public
8 property Font: TFont read fFont write fFont;
9 constructor create(AOwner: TComponent); override;
10 destructor destroy; override;
11 end;
12
13 implementation
14
15 constructor TMyComp.create(AOwner: TComponent);
16 begin
17 inherited create(AOwner);
18 fFont := TFont.Create; //create the Object into the field reference,
19 // so it will not raise an exception
20 end;
21
22 destructor TMyComp.destroy;
23 begin
24 fFont.free; //free the field to avoid memory leaks, etc.
25 inherited;
26 end;
NB: When creating Objects, ALWAYS remember to free them, unless a help file tells
you overwise (happens very rarely, eg exception handlers). Notice that what is
created in the constructor is explicitly freed in the destructor.
This creates a fairly useless component admittedly, but it is an example after all!
When accessing the Font property, it can be referenced in code using:
27 begin
28 with MyComp1.Font do
29 begin
30 Color := clBlue;
31 Size := 10;
32 end;
33 end;
This is all well and good, but what about the Object Inspector?
If we move the property from public to published, the Font property is now
available, with the plus sign to 'drop-down' as required.
This is a step in the right direction.
However, this is not the whole story. What if we were devising a component which
could logically take completely new objects as properties. For instance an analogue
clock face - three similar objects would be obvious.. the hour, minute and second
hands! Each is the same, save for customisable features, such as colour, thickness,
etc.
So - let us construst our AnalogueHand object:
34 type
35 TAnalogueHand = class
36 Colour: TColor;
37 Thickness: integer;
38 end;
Here is an object, descended from TObject, which has the properties we require.
Let us put it into a Clock face component:
39 type
40 TAnalogueClock = class(TGraphicControl)
41 private
42 fHourHand, fMinuteHand, FSecHand: TAnalogueHand;
43 protected
44 procedure SetHand(index: integer; value: TAnalogueHand);
45 public
46 constructor create(AOwner: TComponent); override;
47 destructor destroy; override;
48 published
49 property HourHand: TAnalogueHand index 0 read fHourHand write SetHand;
50 property MinuteHand: TAnalogueHand index 1 read fMinuteHand write SetHand;
51 property SecHand: TAnalogueHand index 2 read fSecHand write SetHand;
52 end;
In the constructor, each field must be created separately, and freed on
destruction:
53 constructor TAnalogueClock.create(AOwner: TComponent);
54 begin
55 inherited create(AOwner);
56 //Set up the Hand Objects
57 fHourHand := TAnalogueHand.create;
58 with fHourHand do
59 begin
60 colour := clBlue;
61 Thickness := 2;
62 end;
63 fMinuteHand := TAnalogueHand.create;
64 with fMinuteHand do
65 begin
66 colour := clRed;
67 Thickness := 2;
68 end;
69 fSecHand := TAnalogueHand.create;
70 with fSecHand do
71 begin
72 colour := clRed;
73 Thickness := 1;
74 end;
75 end;
76
77 destructor TAnalogueClock.destroy;
78 begin
79 fSecHand.free;
80 fMinuteHand.free;
81 fHourHand.free;
82 inherited;
83 end;
84
85 procedure TAnalogueClock.SetHand(index: integer; value: TAnalogueHand);
86 begin
87 case index of
88 0: fHourHand := Value;
89 1: fMinuteHand := Value;
90 2: fSecHand := Value;
91 end;
92 invalidate;
93 end;
Notice that the Hands are written to all using the same procedure, SetHand, each
with a different index to refer to it.
If we install this, we end up with our object, but the object inspector gives an
Access Violation if we try to view the properties - not what we wanted!
The reason being that to descend our Hand Object from TObject is the wrong
ancestor.. For objects which are of a temporary nature, this is fine, but to allow
properties to exist abit longer, to have their properties stored in a persistent
fashion (put very simply!) - we must descend from TPersistent.
So, our new hand declaration looks like:
94 type
95 TAnalogueHand = class(TPersistent)
96 Colour: TColor;
97 Thickness: integer;
98 end;
Rebuild, and the Access Violation has gone - hooray!! But, there are no
subproperties!! An inspection of the Hand object could provide a clue.. With a
standard component, for a property to appear in the object inspector, it must be
published:
99 type
100 TAnalogueHand = class(TPersistent)
101 private
102 fColour: TColor;
103 fThickness: integer;
104 published
105 property Colour: TColor read fColour write fColour;
106 property Thickness: integer read fThickness write fThickness;
107 end;
Rebuild again - and we have subproperties within properties, droppong down without
Access Violations, etc.
At runtime the new subproperties can be accessed by:
108 with AnalagueClock1.HourHand do
109 begin
110 Colour := clOlive;
111 Thickness := 4;
112 end;
113
114 AnalagueClock1.SecHand.Colour := clFuchsia;
This has been a quick and simple overview to providing subproperties in a
component. More complicated user defined objects can be created, which may have
further subproperties (try publishing a TCanvas Object, and see how many layers you
get..).
In summary:
descend your new object from TPersistant (if it is COMPLETELY new - as in the
example);
ensure that any methods declared in the object are written (such as constructors,
setting procedures, functions, etc). - I've forgotten this a few times!!
use the standard of fields and published properties (and any public as required).
The published properties will appear as subproperties.
ensure that when the new object is contained within a component that it is
explicitly created and freed at the appropriate times.
This worked example appears in an expanded form in the component attached to this
article. I had a requirement for a Clock face, but I needed it to be static - for
inputting. All the Clock faces I found were very nice, but the darn things moved!!
So I created my own static analogue clock face.
I make no apology for using British English within the component! Light
diffractions have a 'U' (coloUr), and the free floating state contrary to digital
has a 'UE' suffix (analogUE). If you don't like it - you have the source!!
Component Download: http://www.baltsoft.com/files/dkb/attachment/AnalogueClock.zip
|
