
http://nsis.sourceforge.net/File:NsFlash.zip
Note on dependencies:
This plug-in requires Adobe Shockwave Flash to be installed on the end user's machine. See the example scripts on how nsFlash::IsInstalled is used for this purpose.Stu
5 posts

This plug-in requires Adobe Shockwave Flash to be installed on the end user's machine. See the example scripts on how nsFlash::IsInstalled is used for this purpose.Stu
Yes it's just a habit really now I suppose. It does make it easier to find plug-ins when searching though, and provides plug-ins with a non-generic name without adding many additional characters. What would you have named the plug-in?Originally Posted by AndersWhy do you prefix your plugin names with ns? It might have made sense back when Nullsoft did most of the NSIS work but not really anymore IMHO.
Just referencing the IShockwaveFlash interface in the code requires some CRT initialization thanks to the compiler. The actual ATL functions (such as AtlAxAttachControl) are dynamically loaded though (which keeps the DLL size down a little).Originally Posted by AndersAnd you depend on msvcr110 because you use ATL ActiveX hosting? I am/was working on a plugin that hosts IE but getting the OLE details correctly when doing everything yourself is tricky.
According to MSDN, GlobalAlloc and LocalAlloc are just wrappers for HeapAlloc and using them just adds additional overhead.Originally Posted by AndersWhy use HeapAlloc over GlobalAlloc? You are going to import GlobalAlloc anyway if you use the stack...
Probably something lame like FlashHost.Originally Posted by Afrow UK View PostWhat would you have named the plug-in?
1.0.0.1 - 7th January 2014http://nsis.sourceforge.net/File:NsFlash.zip
* Completely removed msvcr110.dll dependency.
* Replaced HeapAlloc with GlobalAlloc.
* Replaced Flash.ocx import with static interface definition (Flash.h).
* Added /size option for nsFlash::Window.