![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 1 to 5 of 5 total |
![]() |
Thu, Apr 12 2012 4:14 PM | Permanent Link |
Robert Devine | Hi Tim
Would it be possible to get a GroupIndex or similar property for TImage? I've got my own descendant TImage which works fine if dynamically created, but not when I change the declaration of a TImage placed on a form. Cheers, Bob |
Mon, Apr 16 2012 8:20 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Bob,
<< Would it be possible to get a GroupIndex or similar property for TImage? I've got my own descendant TImage which works fine if dynamically created, but not when I change the declaration of a TImage placed on a form. >> This is the one main issue with control descendants - they're simply not supported in the design-time form designer/form files. As for the property, yes, I can see about adding a Tag property. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Apr 18 2012 2:52 PM | Permanent Link |
Robert Devine | Hi Tim
Even although it's not supported in the designer, I'm having success with form inheritance where the descendent forms don't involve any new components added at design time. E.g. I've got a base master-detail form with grid, layout code, panels etc. I then just change the class declaration in new forms and add the code that wires up the dataset. Detail controls are also added at runtime. I thought I might get away with this approach using individual controls but when I changed TImage to TrdImage it wouldn't play ball at runtime - the new property wasn't recognised. Cheers, Bob On 17/04/2012 01:20, Tim Young [Elevate Software] wrote: > Bob, > > << Would it be possible to get a GroupIndex or similar property for > TImage? I've got my own descendant TImage which works fine if > dynamically created, but not when I change the declaration of a TImage > placed on a form. >> > > This is the one main issue with control descendants - they're simply not > supported in the design-time form designer/form files. > > As for the property, yes, I can see about adding a Tag property. > |
Wed, Apr 18 2012 11:12 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Bob,
<< Even although it's not supported in the designer, I'm having success with form inheritance where the descendent forms don't involve any new components added at design time. E.g. I've got a base master-detail form with grid, layout code, panels etc. I then just change the class declaration in new forms and add the code that wires up the dataset. Detail controls are also added at runtime. >> Cool, very ingenious. ![]() << I thought I might get away with this approach using individual controls but when I changed TImage to TrdImage it wouldn't play ball at runtime - the new property wasn't recognised. >> I've got an architecture in my head for 3rd party controls at design-time, so hopefully it won't be much longer after the initial release when I can put it all into place. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Apr 19 2012 5:07 AM | Permanent Link |
Robert Devine | On 19/04/2012 04:12, Tim Young [Elevate Software] wrote:
> Cool, very ingenious I was actually more impressed with your software than the idea ![]() Cheers, Bob |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |