Hi José, A simpler solution would be to specify the callback for the form as a list of two callbacks. Usually you specify a single string (say), but if you look in the documentation you can specify the OK and Cancel action by specifying a list. Then you can have different callbacks for OK/Apply and Cancel. This is definitely simpler than adding back custom buttons each with a callback. For your second question, generally speaking you shouldn't expect the form to return something. It's better practice to use the form callback to do the next phase of your operations. Why is that? Well, if you have an Apply button on the form, the call to hiDisplayForm() won't return - it only returns when you hit OK or Cancel (unless you have set ?dontBlock t when creating the form, in which case it returns immediately). So it's considered bad form (excuse the pun) to rely on the return value from hiDisplayForm(). For your third question, you can customise the help behaviour. It's not that straightforward, but it is covered in the documentation... Regards, Andrew.
↧