Next Button grayed out on custom dialog - why?

[jsmith]

Using the Titanium theme, I have created a custom dialog based on the registration dialog, but with only one text box. I inserted this new dialog in the program flow immediately after the destination dialog. The problem is that when I build and run the installer, the Next> button on this dialog is grayed out. I cannot continue past this dialog. Why is this?


The MSICode looks like:

Display Dialog: badomain, wait for dialog to return (modal)

If I copy and paste it:

~InstallAware Clipboard Data~
~Display Dialog~
~{15A1AFB9-33EF-4713-A1C2-B02025228474}~
~badomain~
~WIZARD~
~TRUE~
~~
~TRUE~
~FALSE~

[jsmith]

Ah, I think I got it. In the badomain.dfm.miaf file, there is logic to disable the next button based on what's in the UserName and UserCompany fields. This logic is causing the button to be inactive even though I deleted one of those text boxes and renamed the other when making my copy of the dialog. Changing the logic in the miaf file so that it has the new name for the text field fixes the button-grayed issue. Shouldn't this have happened automatically when I edited the dialog in the dialog editor?

About the .miaf files - in this thread, "Alex_Ronquillo" says that they can be ignored:

http://www.installaware.com/forums/view ... light=miaf

Given that this file seems to have important logic in it, can it really be excluded from source control?

[CandiceJones]

No, that file is important. It contains your dialog rules - which are also accessible directly in the dialog editor when you double click a control on the dialog. You may edit the file by hand, but be very careful to preserve the exact format; or just use the visual editor integrated into the dialog designer.