Aero plug-in — NSIS Forum Archive

LoRd_MuldeRJanuary 28, 2013 at 11:42 PM#

Originally Posted by LoRd_MuldeR View Post

I had missed that option. Thank you for pointing me at that 🙂

For some reason /btnold for Aero::Apply didn't have any effect on my problem, so I'll just use /CANCELTEXT with inetc.

habenyaminJanuary 30, 2013 at 11:10 AM#

At RTL lang

Aero::Apply and BrandingText At RTL lang ?(farsi)
before Aero adding

After Aero Adding

Hide Branding under cancel and next bt
dose not work with BrandingText TRIMLEFT, /TRIMRIGHT or /TRIMCENTER (farsi)

with option /nobarding just removes BrandingText

Afrow UKJanuary 30, 2013 at 3:52 PM#

There is no support for RTL languages at the moment. I will have to look at it when I have time - I have other priorities at the moment I'm afraid.

Stu

habenyaminJanuary 31, 2013 at 3:18 PM#

بسیارممنون Thank you🙂

Afrow UKFebruary 2, 2013 at 6:41 PM#

New version:

1.0.0.9 - 2nd February 2013
* Fixed button and branding text rendering for right-to-left languages.
* Fixed bug which could cause a crash due to a variable not being initialized to NULL (only when Aero could not be enabled).
* Fixed Aero not being applied on classic UI installers with RTL languages.

http://nsis.sourceforge.net/File:Aero.zip

Stu

LoRd_MuldeRFebruary 3, 2013 at 1:50 PM#

Thank you for the update!

<nitpicking> Seems like you forgot to update the version info. </nitpicking>

Afrow UKFebruary 3, 2013 at 2:55 PM#

Fixed.

Stu

habenyaminFebruary 6, 2013 at 8:23 PM#

thank u so much (to fix it for RTL Lan)

Afrow UKNovember 30, 2013 at 3:39 PM#

New version:

1.0.1.0 - 30th November 2013
* Fixed ampersand handling on branding text.

http://nsis.sourceforge.net/File:Aero.zip

Stu

Afrow UKApril 24, 2014 at 2:35 AM#

New version:

1.0.1.1 - 24th April 2014
* Fixed bug where DWM rect was not invalidated on composition change.
* Added 64-bit builds.

http://nsis.sourceforge.net/File:Aero.zip

Stu

LoRd_MuldeRAugust 29, 2015 at 3:21 PM#

Any chance to fix the font color in Windows 10 when window is inactive?

(Black font on black background is hard to read)

r2du-softSeptember 2, 2015 at 3:20 AM#

Originally Posted by LoRd_MuldeR View Post

Any chance to fix the font color in Windows 10 when window is inactive?

(Black font on black background is hard to read)

Yes,and me too see this problem in windows 10,mr afrow uk if is possible solve this problem...
Thanks

Afrow UKOctober 7, 2015 at 6:03 AM#

The Windows 10 issue has been resolved in the latest version.

http://nsis.sourceforge.net/File:Aero.zip

Note:

The plug-in will detect Windows 10 if you build your installer using:

* NSIS 3.0b2 or newer

* NSIS 3.0b1 with: ManifestSupportedOS {8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}

* NSIS 2.46 or older with: http://nsis.sourceforge.net/File:Packhdr.zip

Stu

LoRd_MuldeROctober 10, 2015 at 11:41 AM#

Afrow UK, thanks for the new version!

However, it took me a long time to figure out why my Installer (made with NSIS 2.46) always failed to start with some strange "Side-by-side" error, after modifying the Manifest with the ResHacker tool. When I inspected the Manifests in ResHacker, it would show that the Manifest of the "working" installer and the one of the "failing" installer are identical, except for the additional Windows 10 compat entry. I even tried removing the compat entry entirely, so the Manifests really were 100% identical - still not working. Bummer !!!

In the end I figured out that the problem is actually the way how NSIS' built-in !appendfile command works! In NSIS 2.46, this command apparently inserts an UTF-8 BOM right at the beginning of the file. ResHacker doesn't show this at all (it silently ignores the BOM), so we cannot see the difference in the Manifest XML code. But with a Hex Editor we can see the BOM is there, even in the embedded Manifest in the final EXE. Original EXE didn't have this. And Windows doesn't like the BOM at the beginning of the XML Manifest at all! It simply refuses to run the installer. So I'm now using a "static" file, rather than a file generated by NSIS' !appendfile command, and all is fine again.

Maybe this info should be added somewhere...

Apart from that, the new version is now working nicely in Windows 10. Great work 👍

Afrow UKOctober 12, 2015 at 11:42 AM#

Are you using a Unicode 2.46 build?

Stu

LoRd_MuldeROctober 12, 2015 at 1:18 PM#

Originally Posted by Afrow UK View Post

Are you using a Unicode 2.46 build?

Stu

Yes.

(I know NSIS 3.x has an /CHARSET option for the !appendfile command, but NSIS v2.46 doesn't)

AndersOctober 12, 2015 at 1:55 PM#

Originally Posted by LoRd_MuldeR View Post

Yes.

(I know NSIS 3.x has an /CHARSET option for the !appendfile command, but NSIS v2.46 doesn't)

Why are you still using the Unicode fork?

LoRd_MuldeROctober 12, 2015 at 2:05 PM#

Originally Posted by Anders View Post

Why are you still using the Unicode fork?

Simply put, it has been working very stable for me for many years.

Also, I have quite a number of projects, which are at a point where we cannot make "major" changes, such as switching the whole install system, from NSIS 2.x to 3.x. The required testing would simply generate too much cost for too little gain.

Nonetheless, switching to NSIS 3.x for future projects as well as for my personal stuff definitely is on my agenda!

AndersOctober 12, 2015 at 3:08 PM#

!appendfile in v3 is ANSI by default unless the file already has a BOM.

Originally Posted by LoRd_MuldeR View Post

Also, I have quite a number of projects, which are at a point where we cannot make "major" changes, such as switching the whole install system, from NSIS 2.x to 3.x. The required testing would simply generate too much cost for too little gain.

The generated installers should be pretty similar, most of the differences between v3 and the fork are in the compiler.

We would of course prefer if as many bugs as possible are found while we are still in beta...

Also, when reporting issues in the future, please say so if you are using an unofficial fork.