How to use multiple forms in one project tutorial up!

[kornalius]

We have a new tutorial on how to use multiple forms in one project.</p>

Check it out:</p>

<a href=&quot;/page.php?44&quot;>http://www.arianesoft.ca/page.php?44</a></p>

</p>

[David Chua]

When using the recommended method the following error occur: &quot;Class PLLForm is already defined for a regular window, use another class name for dialogs&quot;. The opcode that generated this error is: NEWDLG.

However, when I click on the OK button on the error dialog window, the program continue to work normally.

Please advise.

Thanks.

[kornalius]

You need to use another classname for the dialog form. You cannot have the same classname in the same project.

[David Chua]

Yes, I've over look on the Class name. It's OK now.

However, the form ID has to be change as well. VFB default all forms with Form100, in multi form application you will have to change the form ID otherwise, the compiler will complain on the duplicates. Correct me if I'm wrong.

Cheers.

[kornalius]

I don't think so. The ID's a relative to each form. The form ID is not very relevant to Windows API I believe. The Windows API uses the form handle instead. A button ID 100 can appear on two forms the form handle will be transfered to the WinProc with the ID in the parameters. So it should cause any trouble.

[David Chua]

The button IDs are ok. By the way, it's more of the form name actually. Normally, the form name uses its ID to form the name such as Form100, when the VFB generate the code the function performing the task will then be &quot;Form100Proc&quot; and this is the name that gets conflic with the main window or form which has the same procedure name.

I hope you know what I mean.

Cheers.

[kornalius]

Yes the names will need to be different you are right. I will have to come up with something for the next release 1.1. I'll add it to my list.

[David Chua]

Hi Kornalius,

I've tested the multi-form further: Only two thing affected the operation, &quot;Form100Create&quot; and &quot;Form100Proc&quot; which are default. I was thinking you could use the &quot;ClassName&quot; when selecting option to create library. For example, I'm creating a form for configuration purposes so I use the classname as &quot;ConfigForm&quot; therefore, the code will generate &quot;ConfigFromCreate&quot; &amp; &quot;ConfigFormProc&quot;. No other changes required. Further more, it will be easy for me to remember and to call my from, the classname say it all. Hope this helps.

Cheers.

[kornalius]

You can rename the Form name to whatever you like you know?

Instead of Form100 change the &Name property to ConfigForm. Then the code generator will use ConfigFormCreate.

[kornalius]

The problem we will have to solve are the duplicate functions for the controls with the same name in two different forms.

Ex:

MyButton_OnClick on form1 and form2.

We might have to use MyForm_MyButton_OnClick to solve the issue.

[David Chua]

Add/use the classname would be nice in this situation, the calssname got to be different afterall. Besides, it will be easy to be indentified as well. For example, if the new form is &quot;Config&quot; then: ConfigForm100, ConfigFormProc, ConfigForm_Button101..., ConfigForm_Edit102... and etc...

Cheers.