If you wanted to replace grid_ with what you want throughout the project, you would modify grid_ in proctrls.

If you wanted to replace grid_ in all your projects (with certain assumptions) you would modify grid_ in devctrls.

If you wanted to introduce an alternate to grid_ in your project, subclass grid_ in proctrls.

If you wanted to introduce an alternate to grid_ in all your projects, subclass grid_ in devctrls.

The problem with making changes in VPMCtrls, is that when ProMatrix introduces an update, VPMCtrls will be overwritten.

In the case of subclassing, follow the directions in the helpfile for getting proctrls to also hold the empty subclass of the devctrls version.

Hank



>Hi everybody,
>
>I see that the grid class hierarchy is the following in VPM:
>

>Base grid
>           grid_  in VPMCtrls.vcx
>               grid_toolbar in VPMCtrls.vcx
>                    
>
>                  both same classes in DevCtrls.vcx
>
>                            both same classes in ProCtrls.vcx
>

>
>If I would want to introduce a new class here, how should I fit it into this picture?
>
>Introducing top level grdSorting in VPMCtrls would lead to too many subclasses hierarchy. Otherwise, how can I merge my functionality into existing class - hacking?
>
>Thanks again.
>-----------------------
>UPDATE. I hacked the grid and combined them both in VPMCtrls grid_ class. Going to test in a moment.