Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Windows Forms / Design Time / March 2005

Tip: Looking for answers? Try searching our database.

ExpandableObjectConverter not working

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Andy - 17 Mar 2005 19:30 GMT
I have a series of small classes that encapsulate some style
information for some custom controls.  The types of information in
these classes are generally ints, Fonts and Colors.  

I've applied the ExpandableObjectConverter to the various classes to
allow me to expand and set the properties at design time.  The problem
is that it doesn't work reliably.

I have a form in which I test the design-time capabilities of the
various controls.  In that form, which is in the same assembly as all
the expandable types, everything seems to work fine.  I can drill down
through several layers of expandable types and set/view the
properties.

I have a form in another assembly that is part of the same solution
and which contains a reference to the assembly with the expandable
types.  In that form, it's as if the ExpandableObjectConverter was
never applied - the type is just listed, but w/out the plus sign.

I've searched all of the place for information on
ExpandableObjectConveter but have found nothing that gives me a hint
as to the reasons it might or might not work.

Does anyone have any ideas?

Thanks,
Andy
Andy - 17 Mar 2005 20:10 GMT
I've answered my own question.  Dumbness on my part.  It had nothing
to do with the assembly.   It turned out to be only one of my
expandable types that wasn't working, and only where I had added it to
a new control.  

The problem was that I had forgotten to construct the expandable type
in it's parent container.  So when the designer loaded it, there was
not yet a created object instance (of the expandable type) and thus,
it could not be used.

Andy

>I have a series of small classes that encapsulate some style
>information for some custom controls.  The types of information in
[quoted text clipped - 23 lines]
>Thanks,
>Andy

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.