Jason,

I am building an IBO aware version of the VirtualTree view. I am trying to duplicate your paradigm for IBO as much as possible. For one thing, it works, and for another it serves as a model for me to copy.

Question. You have a file called IB_UserClasses.INC. It is real nice for adding user defined classes. Is there something similar I can do with the IB_Controls file and the IB_Editors file? I believe that these are the only two files I have had to modify, other than the IB_UserClasses file.

The IB_Control file had these lines added:
{$DEFINE IBC_VTree}
{$I IBC_VTree.INT}
{$UNDEF IBC_VTree}

{$DEFINE IBC_VTree}
{$I IBC_VTree.IMP}
{$UNDEF IBC_VTree}

And the IB_Editors file had these added:
RegisterPropertyEditor( TypeInfo( string ), TIB_VTree, 'ParentField', TDataFieldProperty );
RegisterPropertyEditor( TypeInfo( string ), TIB_VTree, 'KeyField', TDataFieldProperty );

RegisterDataFieldPropertyEditor( TIB_VTree );

Also, I had to add the component registration to the IB_Registration file.

These are all rather minimal changes, but they need to be done. Any chance of placing some compiler directives permanently in IBO to allow for User defined classes? Maybe there is a better, and cleaner way. But so far this really seems to work great.

Paul


[Non-text portions of this message have been removed]