Problems using Dialog Designer (1.Abort, 2.Move controls)

Hi There,

Firstly, thank you for an excellent and time saving tool. I have found a couple of problems:

1. Skipping a page with Abort

When I have two custom pages created with Dialog Designer, and try to skip the first one with custom code that inserts an Abort, the second page crashes. I suspect the problem is that the code to test if the page is wanted is inserted AFTER the code to create the Dialog Page. Either I need to hand edit the resulting code, or I need to persuade you to allow us to add code BEFORE the dialog is created, much as we can with the MUI_PAGE_CUSTOMFUNCTION_PRE.

2. On a High DPI display, set to 150% scaling, when I move controls, they leave a mess behind that is not todied up until I click elsewhere in the window.

I feel really guilty in not checking for a reply for so long... so thank you for your response.

I wrote up our use of NSIS and the Dialog Designer as part of our internal documentation last year after sending you the original email and added a little information about how to avoid the problem. The attached pdf file (zipped) is a short extract that describes the problem in more detail and my assumption about the cause.

This came about because our application has quite a few Custom dialog pages, and we need the option of skipping pages that are not relevant to the current install.

If you put an Abort in the ControlCustomScript or CreateFunctionCustomScript sections, subsequent use of other Dialog Designer dialogs results in a crash. I cannot recall how I arrived at the conclusion that this was because the handle for the Dialog was already allocated, but Abort in this position abandonned ship without releasing it, resulting in problems later. I discovered that by always having a Show function, I could Abort within that, and then things were OK for subsequent use, so I presume that you trap this and release the handle.

If I am correct about the cause, it should not be too difficult for you to fix it... alternatively folks need warning about this due to the delayed nature of the problem and users who only have a single custom dialog will not see any problem at all.

The installer in which this came up is rather large and has proprietary stuff in it. If this description is not enough for you to identify the problem I guess I can make a project with a couple of dummy pages for you...

Anyhow, I much appreciate this very nice tool and thank you for providing it,

Greg Smith