Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread TCustomButton
Thu, Oct 25 2018 10:00 AMPermanent Link

ooptimum

Hello,

It seemed to me quite an obvious idea not to create a separate class for each type of (colored etc.) buttons that I need, but to create one universal control and link it to different interfaces as necessary.

Now I have a few questions regarding handling this component in the design mode:
1. How to find out whether the interface class name is valid?
2. How to make so that when you change the interface class name, the appearance of the button also changes in the IDE?
3. How to get rid of the "[Interface Manager Debug] Warning: interface class bla-bla not found and not applied"?

The component and an example project are attached.



Attachments: CostomButton.zip
Tue, Oct 30 2018 2:17 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com


<< It seemed to me quite an obvious idea not to create a separate class for each type of (colored etc.) buttons that I need, but to create one universal control and link it to different interfaces as necessary.

Now I have a few questions regarding handling this component in the design mode: >>

Unfortunately, for design-time you'll have to pick a "default" interface and use it.  In the meantime, I'll see what I can do about surfacing the interfaces in the same manner as at run-time.  I can't really think of any downsides or issues with doing so, but you never know...

Tim Young
Elevate Software
www.elevatesoft.com
Image