Dialogs 6.1 vs 6.2?

[jsichak]

I was wondering if there was a faq that details the differences between DD 6.1 and 6.2.  Do you recommend converting current 6.1 dialogs over to 6.2?

[td]

Wouldn't bother unless you decide to modify your dialog by adding some feature only available using the 6.2 template.  You will know when the feature is not supported by the 6.1 template because you will get an error message when you try to make use of  the feature in the 6.1 dialog.

The three biggest enhancements in 6.2 dialogs are that you can make more modifications to the dialog in the WIL Dialog Editor without completely ruining your dialog callback procedure, add both context and menu bar menus to your dialog, and make use of the new REPORTVIEW control.   

[jsichak]

Thanks Td.

[cssyphus]

There is also one extra parameter in the dialog control definition:

6.2
<dlg-variable>nn =`x, y, width, height, type, control-name, var/license-string, text/pre-selected item/progid/classid/moniker, value, tab-order, style, font, textcolor, backgroundcolor`

6.1 lacks the 6th parameter "control-name"

In 6.1, we refer to each dialog control by its dlg-variable.  Not an important difference, but one you must always keep in mind if accustomed to the 6.2 dialogs.

[Deana]

Probably no need to convert unless you require the newer functionality. 6.1 Dialogs continue to work fine.

Changes to the Dialog function and related functions:
New 6.2 dialog adds a required 'Name' attribute to control definition strings. The new attribute is passed as the third parameter to user-defined-callback procedures and must be used as the second parameter to the DialogControlSet, DialogControlGet, DialogControlState, and DialogObject functions. Note: 6.1 style dialogs are still fully supported. DialogControlState now returns the control name of the control with the input focus and an empty string when using request-code 5 and no control has the input focus. (Applies to dialogs with 6.2 or later format only) The User Defined Dialog Callback function now receives a control name instead of control number in the third parameter. (Applies to dialogs with 6.2 or later format only) The function DialogControlSet, DialogControlGet, DialogControlState, and DialogObject now take a control name instead of a control number as their second parameter. (Applies to dialogs with 6.2 or later format only) Added new request 17 to DialogControlGet/Set. Retrieves/sets the size and location of a control within a dialog's client area.

Reference:  http://www.winbatch.com/winbatchversions.html#WB2008E

[td]

There is also one extra parameter in the dialog control definition:

6.2
<dlg-variable>nn =`x, y, width, height, type, control-name, var/license-string, text/pre-selected item/progid/classid/moniker, value, tab-order, style, font, textcolor, backgroundcolor`

6.1 lacks the 6th parameter "control-name"

In 6.1, we refer to each dialog control by its dlg-variable.  Not an important difference, but one you must always keep in mind if accustomed to the 6.2 dialogs.

The use of the 'control-name' instead of a control number is what allows 6.2 dialogs to be edited via the Dialog Editor without the the dialog mangling that often broke dialog user defined callback functions/subroutines.

[kdmoyers]

6.2 was a blessing if you ask me.  If you are starting anything new, for goodness sake, use 6.2
-Kirby