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

Please let our ADS show!

This sites offers only FREE software and it's supported by a few advertisement boxes (no intrusive popups).
Please:

  • disable your AdBlocker by adding CoolSoft website to whitelist
  • give the proper cookie consent
  • enable JavaScript for this website

This seconds wait is to let you update your browser configuration...

Ok, I've done the required changes... now show me your content!
!!! Please enable JavaScript !!!
Posts: 1
Joined: December 7, 2021 - 23:01
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.

Posts: 1886
Joined: March 25, 2012 - 01:19
Re: Problems using Dialog Designer (1.Abort, 2.Move controls)
Greg Smith wrote:
1. Skipping a page with Abort

Should be great to have 2 samples:

  1. sample project created with NSISDialogDesigner (the one that crashes)
  2. same project + your fixes, to show me what's missing

Comparing the two I'd like to be able to find what's missing in the editor and/or if there's a better way to accomplish your requirements.

NOTE: sample projects must be as simpler as possible, with only the elements needed to show the issue.

Greg Smith wrote:
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.

Well, the dialog designer was built with .NET 2.0, when HighDPI screens were not so widespread.
I suppose .NET 2.0 is not fully HighDPI-aware 🙄

Should have a look at it and upgrade to 4.x, but I can't make any promise...