It has to be dynamic. No idea how many objects or what type at design time...
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of russell Sent: Friday, 13 July 2012 7:35 p.m. To: 'NZ Borland Developers Group - Delphi List' Subject: Re: [DUG] Creating an object at run time. Are there reasons you would avoid making the objects at development time as not visible and making them visible only when needed? Stated without negatives, make the objects now, make them invisible and when needed make them visible. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: Friday, 13 July 2012 3:21 p.m. To: NZ Borland Developers Group - Delphi List Subject: [DUG] Creating an object at run time. I want to create an object at runtime given a string with the object type. Is this possible or do I need to do a whole pile of if then else's? There is a limited number of different objects that need to be created. I then want to access the created objects properties by name and assign methods. This is not for oleobjects, but VCL controls. i.e. b := CreateObject('TButton') ; b.GetField('left') := 100 ; ... Help on any of these would be appreciated. Cheers, Dave. _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
