Leave the original ppPrvDlg.pas alone. Rename your visual form as myPrvDlg.pas so that the form class name is different than the one in RB. Now you can still use RBuilder\Lib dcu's because you can register this new form class with RB and you do not have to recompile our source. See the Tutorials section in the Developer's Guide PDF. The coded example is located in the RBuilder\Tutorials\Complete\Applications\rbPrvDlg.pas. If you start with the ppPrvDlg file in the tutorials, then you don't have to recode the implementation of the form. You should notice that the ppPrvDlg.pas uses a preview plugin architecture which creates the controls in code. Instead of replacing the form, you can replace the preview plugin. The advantage to changing the plugin is that you can affect both the preview form and the preview tab of the end user designer. If you only change the form visually and register a replacement for the ppPrvDlg.pas, then you'll only affect the preview form and not the designer since the designer uses the preview plugin architecture and not the standalone preview form.
Comments
Leave the original ppPrvDlg.pas alone. Rename your visual form as
myPrvDlg.pas so that the form class name is different than the one in RB.
Now you can still use RBuilder\Lib dcu's because you can register this new
form class with RB and you do not have to recompile our source. See the
Tutorials section in the Developer's Guide PDF. The coded example is located
in the RBuilder\Tutorials\Complete\Applications\rbPrvDlg.pas. If you start
with the ppPrvDlg file in the tutorials, then you don't have to recode the
implementation of the form. You should notice that the ppPrvDlg.pas uses a
preview plugin architecture which creates the controls in code. Instead of
replacing the form, you can replace the preview plugin. The advantage to
changing the plugin is that you can affect both the preview form and the
preview tab of the end user designer. If you only change the form visually
and register a replacement for the ppPrvDlg.pas, then you'll only affect the
preview form and not the designer since the designer uses the preview plugin
architecture and not the standalone preview form.
Here is an example of replacing the preview plugin:
http://www.digital-metaphors.com/tips/AddControlsToPreview.zip
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com