dade plugin with custom TdaQueryDesigner

rbuser

im building a dade plugin and need to use a custom window for the user to
design the dataview. Is there any information available that can help me?

I have noticed that there seem to be two ways to load a custom designer.
One way by creating a descendant "TdaQueryDesigner", and the other by
creating a descendant "TdaCustomDesignDataDialog"??? these descendants can
then be specified in my new DADE plugin by overriding the class functions
"DataDesignerClass" and "DesignFormClass". these are used in the
TdaDataWizardManager.DesignDataView function to load the design window

I am going down the right track, because even after registering my
descendant TdaQueryDesigner in the daIDE unit, it still loads the
TdaQueryDesigner and not my descendant. without registering in the daIDE
unit it doesnt open any design window.....

could someone please clarify the basic steps that are neccessary to create a
new custom design window for my plugin?

many thanks
Cameron hart

nardmoseley

I just wrote the following tech tip......

----------------------------------------------------------------------------
------
Tech Tip: Implementing a Custom Data Designer
----------------------------------------------------------------------------
------

Data Designers descend from TdaCustomDataWizard which is defined in
daDataWizard.pas.

The TdaCustomDataWizard class defines a class function called DataViewClass
that should be overriden by descendants classes to specify the DataView
class for which the data designer is implemented.

The daRegisterWizard and daUnRegisterWizard procedures defined in
daDataWizard.pas are used to register and unregister Data Designers with
DADE.

For an example of a data designer, see daQueryDesigner.pas which contains
the default QueryDesigner. The TdaQueryDesigner class overrides the
DataViewClass method to return TdaQueryDataView. Therefore, the
QueryDesigner is used with any descendant of TdaQueryDataView
(TdaADOQueryDataView, TdaBDEQueryDataView, etc.).

For an example of registering a Data Designer, see the initialization and
finalization sections of daIDE.pas.

Note: To replace an existing Data Designer, unregister the default designer
first:

initialization

daUnRegisterWizard(TdaQueryWizard);
daUnRegisterWizard(TdaQueryDesigner);

daRegisterWizard(TmyCustomQueryWizard);
daRegisterWizard(TmyCustomQueryDesigner);

finalization

daUnRegisterWizard(TmyCustomQueryWizard);
daUnRegisterWizard(TmyCustomQueryDesigner);





--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com

rbuser

thanks nard