Ultra-Modern UI

thanks for your answer, i will do it with my owner installers but i also get the poroblem with the installer of Ultramodernui...

Sad for the visa users if they can't correctly install the program itself...

New build version 2008-08-09

_ Fixed: The Welcome/Finish/Abort pages text use the default font size
_ Added: A new define named "UMUI_WELCOMEFINISHABORT_TITLE_FONTSIZE" to change the font size of the Welcome/Finish/Abort pages title. By default this value is set to 12 for default pages and to 8 for the alternative pages.
_ Fixed: A little more mistake in the English language file.
_ Fixed: The AlternativeStartMenu page disable creation shortcut checkbox is shown even if the shellvarcontext options is disabled.
_ Fixed: The UMUI_INSTALLERFULLPATH_REGISTRY_VALUENAME define that was saved with the default value even if the $INSTDIR variable is modified in the DIRECTORY page.
_ Fixed: Bugs in example scripts (e.g.: Maintenance, Update...).

Download

Thank you for the update 🙂

But still no fix for the Vista button problem, too bad...

I maked a test:
- WinXP x86, buttons ok
- WinXP x64, ?
- Vista x86, buttons ok (business)
- Vista x86SP1, buttons ok (ultimate)
- Vista x64, ?
- Vista x64SP1, no buttons (ultimate)

So, i think the x64 or the SP1 for x64 is the source of the problem. (as i see, the UAC or Windowblins doesn't matter)

I have installed a Vista x64 SP1 Ultimate on my PC and I have no problems. (It was a DVD with SP1 slipstreamed by vlite)

I will try to install it in a VMWare. (the RTM version and next, the SP1)

Me to(just to the testing): Vista x64, SP1 included Unlimited
And i don't know why, but no buttons. 🙁

You are right, no button with Vista x64 + SP1.
Without SP1 it works.

I will make a workaround that disable buttons skin if Vista x64+sp1 is detected.

That's would be great. 👍

Originally posted by evin
That's would be great. 👍

Yup 😎

But maybe it would be safer to disable skinned buttons for all versions of Vista x64 that are equal or newer than SP-1, since we must expect that future Service Packs will have the same problem, unless the opposite is proven...

IMHO skinned buttons could be disabled completely for Vista, since I don't care about Vista as long as I don't get any error reports 😉

SuperPat,

I would like to bring to your attention a bug that I am experiencing. With your latest version of UltraModernUI, if a MessageBox is displayed in a custom leave function via MUI_PAGE_CUSTOMFUNCTION_LEAVE, some of the buttons on the following screen will not be skinned. This can be demonstrated by the attached script. I'm not sure what's going on, but I think it's in the SkinnedButton plugin. Is there any way you could look in to this?

Thanks.

I know this problem, but I do not know how to fix it...

If anybody known a solution, for this problem, for buttons unskinned with InstallOptionsEx and for buttons unskinned if XPStyle at "on" and if you use vista x64 SP1.

New build version 2008-08-15

_ Fixed: Workaround for the SkinnedControls plugin one Windows Vista x64 SP1 and more that not drawn buttons at all. (Buttons are now unskinned on this system version)

Download

Thanks for the update 😁

Just a few hours after I released an update of my installer 🙄

thanks a lot!

I am on my "other" computer which I don't use for work. I have installed the last UMUI version.

There is problem with language page:

!insertmacro: UMUI_UNPAGE_MULTILANGUAGE

Usage: CreateFont $(user_var: handle output)

face_name [height wieght /ITALIC /UNDERLINE /STRIKE] 

Error in macro UMUI_FUNCTION_MULTILANGUAGEPAGE on macroline 168

Error in macro UMUI_PAGE_MULTILANGUAGE on macroline 41

Error in macro UMUI_UNPAGE_MULTILANGUAGE on macroline 7

Error in script "D:\pospec\UltraModernUI_1.00_2008-08-15\

Examples\UltraModernUI\MultiLanguage.nsi" on line 51

 -- aborting creation process

🙁

It seems to be quotes problem:

UMUI.nsh line 5175: CreateFont $MUI_TEMP2 "$(^Font)" "${UMUI_WELCOMEFINISHABORT_TITLE_FONTSIZE}"" "700"

It went wrong in UltraModernUI_1.00_2008-08-09 version. I wonder that nobody experienced this bug 🤪

Sorry for three consequent posts, maybe moderator could merge them...

New build version 2008-08-16

_ Fixed: Compilation bug with MultiLangage Page (Thanks pospec)

Download

Il n'y a pas de quoi! 😉

SuperPat, I got feedback from the Vista user. Your workaround seems to work 🙂

Thanks again!

I have a couple of problems with password fields from installoptions ini files.

First Problem:
When a user types in a password field, then hits the backspace key, the carret moves back but the * characters remain. When they then type, the carret moves forward again and the * characters that were there before backspace remain until the user types past the end of them.

Second problem:
A user types in the field, then holds ctrl and hits home, the text is highlighted as expected, however, no matter what they type, the highlight stays and all the existing * characters remain, then behavior is like the first problem.

In short, the UI for a password field does not operate as expected. It does, however, operate fine when used in a non-UltramodernUI interface. Any help here would be appreciated.

I've just switched to using UltraModern UI, mainly because I want to produce a custom look and UMUI seems to handle skinning+ResHacker very well.

I do have one small problem, which I've brought upon myself. I've used ResHacker to move around the components in Dialog 105. And I mean I've moved EVERYTHING around, especially the Header text blocks, which I've shifted down to be right above the big work area. I've also resized the dialog. Generally speaking, it works.

My install script is just a test version of "basic.nsi" that comes with UMUI. I've turned on the Welcome and Finish pages, but not customized them. When I run the installer, everything is great until I get to the Install page. Right before it switches to the Finish page, for a split second, the header text gets what looks like "Installation Complete" written on top of it, such that they both appear at the same time. Then it switches to the Finish page.

It happens so quickly that I can't do a screen capture. Blink and you miss it.

When I switch back to an unhacked UMUI, I don't get the problem, leading me to think that I've moved something -- or perhaps *failed* to move something -- so that the original header text isn't being blanked out.

Another clue: If I don't have a Finish page, the behavior still happens, but the text is replaced with "Installation Complete" and "Setup was completed successfully", which is displayed correctly. There's still a brief flash of overwritten text.

I'm guessing most (all?) developers have not experienced this problem, because hacking the UI is thankfully not the norm. 🙂 But I would appreciate any advice anyone may have about fixing this problem.

Thanks in advance for any help or advice!

Michael

Can you join the exe and eventualy the hacked exe so that I look

Thanks for the reply! How do I join them? And how do you want me to send them to you?

with your reply on this forum

D'ohh! Instead of giving you my production script -- too many dependencies for you to compile -- I've given you your "basic.nsi" script updated with the new look. It exhibits the same behavior, though it's right before the StartMenu page displays. (Since on my machine that page takes a while to display.)

The complete setup is included in the attached .zip. Let me know if I've left anything important out.

Thanks again for your help. Please don't spend too long on it!

Michael

Yopu are right, the text you seen is well:
"Installation Complete"
"Setup was completed successfully."

This is normal behavior of MUI. we can see it with UMUI because I have added some instructions at the end of the finish function.

I will release a new version immediately.

New build version 2008-09-20

_ Updated: NSIS to version 2.39
_ Added: New Skin WhiteBlue
_ Fixed: Reduce flicker at the end of the installation

Download

SuperPat, you are awesome! Thanks for fixing it. I will be happy to test it for you when it's available. 🙂

Michael

SuperPat, another question while you're poking around in the code... There are currently several bitmaps used in the background of the installer dialog. (The left image, header image, bottom image and center image.) My design doesn't have five images, just one. For my skinning purposes, having so many images makes things harder, because I need to slice up my design into pieces.

If I were to remove four of the image resources and resize the center image to be the full height and width, will that harm anything. Does the interface get messed up if an expected resource is missing? (I believe I already eliminated the left image, and it seems to work, but maybe I am pushing my luck. 🙂 )

Also, I just noticed the UMUI_CUSTOM_SKIN define, which makes my skinning better, since I need to keep my skin files separate from the normal NSIS code. I can see you really put a lot of thought into this!

Thanks!
Michael