Using classes not derived from control at design time?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Toma Catalin - 17 Jul 2008 10:12 GMT

Hy there, I am working on a project and I want to add design time support. My
problem is that I don't want to create controls. For example,some times I
just need a class tat has a location,size and an Image propoerty, and I want
to set this properties at design time. I don't need to derive from Control.
Is there any way I can create a lightweight control+designer? A control has
hundreds of properties..they slow down my application. I just want to drag a
class on the form and to see serialized code for 3 properties.
Thanks in advance.

Signature

Toma Catalin, Microsoft Student Partner

Reply to this Message

eschneider - 21 Jul 2008 20:54 GMT

Try making a simple control with you three properties and mark all unneeded
properties with:

[DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden)]

You can also use properties ShouldSerialize[Property Name] to dynamically
determine serialization.

You may need to shadow existing properties to hide them.

Schneider

> Hy there, I am working on a project and I want to add design time support.
> My
[quoted text clipped - 9 lines]
> class on the form and to see serialized code for 3 properties.
> Thanks in advance.

Reply to this Message

Toma Catalin - 22 Jul 2008 11:14 GMT

My problem is the hierarchy behind the Control. Plus, it has a HWND, so it's
like I am creating a form without a border. For most of my needs,I don't need
messages to be passed to my visual classes. I know I can hide all code
serialization, bot it's still a Control that is derived and implements a lot
of classes and interfaces, wich I don't need.

I started deriving my classes from Component, but I still can't write a
designer that will show my Component at design time on the visual surface...

Signature

Toma Catalin, Microsoft Student Partner

> Try making a simple control with you three properties and mark all unneeded
> properties with:
[quoted text clipped - 21 lines]
> > class on the form and to see serialized code for 3 properties.
> > Thanks in advance.

Reply to this Message

eschneider - 23 Jul 2008 21:33 GMT

All controls are forms underneath, there is no way around it.

Maybe you want to create your own design surface (like a custom drawn design
surface), otherwise I think what I suggested it the best approach.

Schneider

> My problem is the hierarchy behind the Control. Plus, it has a HWND, so
> it's
[quoted text clipped - 38 lines]
>> > class on the form and to see serialized code for 3 properties.
>> > Thanks in advance.

Reply to this Message

Using classes not derived from control at design time?

Free Magazines