Hi,
I have an installation program that works just fine on XP, 2000 and what not. However, on Vista, I have a strange problem with just SOME of the screens.
So, some screens are ok and looking like the first attachment (screen1.jpg) (ignore the white messy 'rectangles'). Others are not ok and looking like the second attachment (screen2.jpg). This means that the title (Welcome to ... Setup), the progress buttons / text and the logo (white area above the cancel button - removed from this screen for obvious reasons) are not showing in the second screen. However, going past a faulty screen and back to it makes it show ok. Even stranger, if I press ALT key on a faulty screen, makes it display ok (no going forward/back needed).
The black background is an image, same is the white square.
What am I doing wrong?
(Edit: seems I cannot attach two files so I am making only one, screen1 is the top picture, screen 2 is the bottom one).
File Attached:
both_screens.JPG
Vista UI strange issues
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
You can try re-setting your theme, or compare properties for objects in dialogs that don't work with the object properties in the dialogs that do work - and fix them.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
-
eugen.cocalea
- Posts: 15
- Joined: Tue Feb 17, 2009 12:54 pm
Some more information:
I have 8 screens in my installer, three of which do not work. Two of them have in common the fact that they have one edit box. The third has a memo in it. Making the edit box 'Visible' property 'False', makes the installation draw the screens correctly. Setting 'Visible' to 'False' for memo does nothing, the memo displays ok (just that it disappears from the editor and I have to 'test' the screen to get it back).
Really strange.
Edit: I am talking about the edit box that has 'c:\\program files' in it in the second screen of the attachment.
Another edit: There is a bug / feature in the dialog editor as well. Set an object visibility to false, save the dialog, close the editor, open the dialog. The object doesn't show in the editor until you 'Test' the dialog.
Yet another edit: InstallAware Studio 8.
I have 8 screens in my installer, three of which do not work. Two of them have in common the fact that they have one edit box. The third has a memo in it. Making the edit box 'Visible' property 'False', makes the installation draw the screens correctly. Setting 'Visible' to 'False' for memo does nothing, the memo displays ok (just that it disappears from the editor and I have to 'test' the screen to get it back).
Really strange.
Edit: I am talking about the edit box that has 'c:\\program files' in it in the second screen of the attachment.
Another edit: There is a bug / feature in the dialog editor as well. Set an object visibility to false, save the dialog, close the editor, open the dialog. The object doesn't show in the editor until you 'Test' the dialog.
Yet another edit: InstallAware Studio 8.
-
eugen.cocalea
- Posts: 15
- Joined: Tue Feb 17, 2009 12:54 pm
And more:
Putting any of the faulty screens as the first dialog in the installation, makes it work. Subsequent faulty screens do not.
Ok, as I was writing this, I found how to fix this, although I don't know what was wrong. The background image (the gray gradient) was bigger than the screen. Making it exactly the size of the screen and reloading it in every screen solved the problem.
Still don't know why this is an issue only in conjunction with text input and memo.
Putting any of the faulty screens as the first dialog in the installation, makes it work. Subsequent faulty screens do not.
Ok, as I was writing this, I found how to fix this, although I don't know what was wrong. The background image (the gray gradient) was bigger than the screen. Making it exactly the size of the screen and reloading it in every screen solved the problem.
Still don't know why this is an issue only in conjunction with text input and memo.