demiller9
11th June 2010 22:05 UTC

Vanishing controls
  I am using MUI2 and have a problem with controls being drawn when the custom page appears, but 5 seconds later the control (text, radio button, etc) disappears. If I move another window in front of the dialog and then move it away, the text will reappear. I'm running on Windows XP, compiling with NSIS 2.46.

I know that this was a symptom when the controls overlap with another control, but I'm sure that I don't have any overlapping controls on the page in the screen shot here. This page has only two controls on it and was created with code like this:

nsDialogs::Create 1018
Pop $0
${NSD_CreateLabel}  0u 0u 100% 11u "The following messages show failed components or indicate actions are required."
Pop $0
${NSD_CreateListBox}  0u 20u 100% 67% ""
Pop $ErrorsPage.hLBox
... # code to fill the list box
# Display the page.
nsDialogs::Show

Can anyone help me figure out why these controls are disappearing?
Thanks

Anders
11th June 2010 22:42 UTC

I can't reproduce this (XP:SP2 hacked uxtheme with custom VS)

outfile "$%temp%\test.exe"

>RequestExecutionLevel user

>!include MUI2.nsh

>function cust

>!insertmacro MUI_HEADER_TEXT "hello world" "lalalalalalalalalala"

>nsDialogs::Create 1018

Pop$0

>${NSD_CreateLabel}  0u 0u 100% 11u "The following messages show failed components or indicate actions are required."

>Pop $0

>${NSD_CreateListBox}  0u 20u 100% 67% ""

>Pop $0

SendMessage$0 ${LB_ADDSTRING} 0 STR:Hello

SendMessage$0 ${LB_ADDSTRING} 0 STR:World

nsDialogs::Show

functionend


page custom cust

>!insertmacro MUI_LANGUAGE "English"

>section

sectionend 

>

Animaether
12th June 2010 00:45 UTC

no repro here either.. XP SP3 with default theme (yeah, that ugly candy thing)

demiller9
12th June 2010 00:50 UTC

Well, it's obviously something running in my system that's causing it. I cut/pasted Anders' code and it exhibits the same behavior. I'll track it down and figure out which program is doing it.

I just was concerned that my setup programs might do that on our customers' systems; now it appears unlikely.

Thanks for checking your systems, Anders and Animaether. When I find what causes it I'll post a followup.

Don

edit: attach screen shot from Anders' script

demiller9
12th June 2010 02:40 UTC

Solved!
  I tracked down the offending program; it was ipoint.exe (version 6.1). Microsoft had a newer version for my mouse (7.1) and the problem is gone now.

Animaether
12th June 2010 03:06 UTC

glad you found the culprit.. wonder what part of that driver messes with UI drawing. ah well :)

CrushBug
15th June 2010 18:51 UTC

Wow, this might be the cause of the problems we have seen with NSIS at our end. I am going to grab this driver and roll back our nsDialog changes and see if this problem goes away. A lot of us have MS mice and the IntelliPoint 6.x drivers. I will try the 7.0 driver and get back to you when I can.