http://msdn.microsoft.com/library/en...etpropbrow.asp
Make Your Components Really RAD with Visual Studio .NET Property Browser
Summary: This article will help you explore the Microsoft Visual Studio .NET
property browser and take advantage of its new features. (23 printed pages)
Check out this section:
Expandable Properties and String Conversion: TypeConverters and the Property
Browser
One of the great features of the Visual Studio .NET property browser is the
ability to display nested properties, allowing for a more granular and
logical level of grouping than categories. Nested properties are also
available in both categorized and alphabetical sort mode. It helps keep
property lists compact-instead of both a Left and Top property, just a
Location property that is expandable into X and Y will do for a separate
entry.
--
Greetz
Jan Tielens
________________________________
Read my weblog:
http://weblogs.asp.net/jan
"Edward Diener" <ed******@tropicsoft.com> wrote in message
news:eH**************@TK2MSFTNGP09.phx.gbl...
I am creating a component and I want one of my properties to be an
embedded class with its own properties. When the component designer shows this
property I want it to be able to expand this property in-line to enable
the end-user to set its values. While my component is derived from
System::ComponentModel::Component, my embedded class has to be derived
from something else in order for it to be shown as an embedded class but be
serializable and marshallable at the same time. What is this something
else ? Does my embedded class need to be of a value type to be embedded in this
way or does it just need to be derived from a different .NET framework
base class ?
As an example in C++ Builder, if I derived my component from TComponent,
it was treated as a component. If I derived my class from TPersistent, it was
treated as an embeddable class. What is the .NET equivalent to the latter
?