Infralution Support

[gregoryagu]

It is interesting that you use the name Widgets in the Virtual Tree. The thing I don't understand is that typically a widget refers to a GUI element, but in your case, it refers to a windowless element.

I really like that you use a Widget for much of the code so that it can be subclassed without the overhead of subclassing the entire control to modify a part of the behavior.

Is there any more information this pattern that you would care to share? I use a similiar pattern wherein any logic for a Windows Form is contained is a seperate class, but I usually call that a Manager for lack of a better name. But I think the principle is along the same lines.

Just curious!

Greg

[Infralution]

You can think of a Widget as just a windowless (or lightweight) control. It supports many of the same methods as a control but instead of having its own window it renders to its parent WidgetControls window. Most windowing frameworks have support for something like this - but Windows Forms doesn't.
_________________
Infralution Support