MSIBanner - newest plugin

Really? 😁

So, will be later on the web archive plus in my server... 🙂

Thanks to you all for testing it.... 😉

Yes, no more crashes 🙂
But installer after banner still goes to background on Win2K 🙁

Is there any documentation for this? (I think it would be helpful for us all to know exactly what functions are available to test.)

Great work on this, by the way!

erm... see examples? :|

I just thought that perhaps you had more undocumented properties/procedures you'd like to have tested, but from the sounds of it, what's in the examples is all there is.

In response to Takhir:

But installer after banner still goes to background on Win2K

I've compiled all the included examples on my Win2K computer using NSIS 2.04 and did not see the same symptoms--the installer always stays in front. Were those tests done with the included example scripts or something different?

This happens on my comp with all (3) included nsi examples. Win2K Server Rus, SP2, NSIS 2.04. Pentium II 400, 256 MB 🙂
I see installer page for a short time (~0.5 sec) in the foreground, but after this page goes to background, while it's task bar item continue flashing (focus not lost?).

hmmm, Strange...
My PC is Win2k Pro w/ SP4. Do you think the SP might be the problem?

(I'd test it, but unfortunately, I don't have any spare Win2k computers...)

This may be slow comp...
BTW KichiK also wrote about background problem (4-th post of this thread).

BTW KichiK also wrote about background problem

Yes, but was before adding the feature 😉

I was experimenting with the banner on an XP pro computer and Win2K. I seem to get fairly consistant errors whenever I use a silent installer with the banner and a message box displaying with the .onInstSuccess callback.

Here's a simplified example script:

!define PRODUCT "MSIBanner"



Name ${PRODUCT}

OutFile "${PRODUCT}2.exe"

ShowInstDetails show

;XPStyle on



Function .onInit

SetSilent silent

MSIBanner::Show /NOUNLOAD "NSIS Installer - ${PRODUCT}"

MSIBanner::Move /NOUNLOAD 20 "Countdown to destruction 5"

MSIBanner::Pos /NOUNLOAD 100 "Cleaning...."

FunctionEnd



Function .onInstSuccess

   MessagebOX MB_OK "DONE!"

FunctionEnd



Section -default

MSIBanner:😁estroy

DetailPrint "Works great!"

SectionEnd

If I remove the calls to MSIBanner, it seems to work fine. It also seems to be ok if I REM the SetSilent line. (Example error is attached.)

Of course... there aren't windows or dialogs which the banner attached to it...

The MSIBanner isn't a standalone one 😉
Needs a parent window.

BIG EDIT:
Just test the code ... and I don't get any errors:

!define PRODUCT "MSIBanner"



Name ${PRODUCT}

OutFile "${PRODUCT}2.exe"

ShowInstDetails show

;XPStyle on



Function .onInit

SetSilent silent

MSIBanner::Show /NOUNLOAD "NSIS Installer - ${PRODUCT}"

Sleep 1000

MSIBanner::Move /NOUNLOAD 20 "Countdown to destruction 5"

Sleep 1000

MSIBanner::Pos /NOUNLOAD 100 "Cleaning...."

Sleep 1000

FunctionEnd



Function .onInstSuccess

   MessagebOX MB_OK "DONE!"

FunctionEnd



Section -default

MSIBanner:😁estroy

DetailPrint "Works great!"

SectionEnd

Be sure to have the lastest version of the MSIBanner...
WOW! Works even in silent mode 👍

Your explanation makes perfect sense! (And once you do it right, it works like a charm!)
😉
Thanks!

2 new questions:
I have situations where I launch applications during an install. The applications I use a banner page that displays while the app is initializing. The problem is that the banner of the other apps covers MSI Banner's window.

Is it possible to force the MSI Banner to the top of all other windows? Or is it posible to set the position of MSI Banner on the screen?

Try using BringToFront to bring the installer to the top.

-Stu

Is it possible to force the MSI Banner to the top of all other windows?

Do what Stu said 😁

Or is it posible to set the position of MSI Banner on the screen?

Maybe on next release 😉

Thanks guys!

could you make it support InstallColors and InstProgressFlags in future?

Originally posted by Joel
The MSIBanner isn't a standalone one 😉
Needs a parent window.

i take it that's why the attached example doesn't work?