>How about adding a new constructor to TMybutton and creating it in the
>form create
Wot, create a second button (TMyButton) and assign Button1 to it?! Like
procedure TForm1.FormCreate(Sender: TObject);
var TempButton: TMyButton;
begin
TempButton := TMyButton.Create(Button1);
Button1.Free;
Button1 := TempButton;
end;
Yuck... :)
>The ideal situation would be for the IDE to operate as an interpreeter
rather >than requiring
>compiled components and implement a complete subclassing engine... Of
>course this is
>rapidly drifting toward java territory instead of delphi ;)
Is the IDE too responsive for you, Aaron? :) Ooh... invites flames...
best change subject... well, you did mention that "J" word. :)
Come on everyone, haven't any of you ever wanted to subclass a component
on a form without either sticking yet another
"TAnotherSubclassedComponentThatsNeededForOneParticularFormButICouldntTe
llYouWhyOrWhatItDoesWithoutLookingAtItAgain" component into the
component palette, or creating and keeping track of "helper objects"?
One of the advantages of my suggestion is that it would be very easy to
implement. One tiny extra situation to check for during a compile and a
slight relaxing of the loading rules - that's it! :)
It was next on my list in Delphi 1 after form inheritance.
Cheers,
Carl Reynolds Ph: +64-9-4154790
CJN Technologies Ltd. Fax: +64-9-4154791
[EMAIL PROTECTED] DDI: +64-9-4154795
PO Box 302-278, North Harbour, Auckland, New Zealand
12 Piermark Drive, North Harbour Estate, Auckland, NZ
Visit our website at http://www.cjntech.co.nz/
> ----------------------------------------------------------------------
> -----
> New Zealand Delphi Users group - Offtopic List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
application/ms-tnef
