From da90e3b38951734ee11af3530546345175114c9a Mon Sep 17 00:00:00 2001 From: kichik Date: Sun, 22 Sep 2002 11:34:58 +0000 Subject: [PATCH] Plugin docs fixes (/NOUNLOAD flag stuff) git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@1136 212acab6-be3b-0410-9dea-997c60f758d6 --- Docs/src/plugin.but | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docs/src/plugin.but b/Docs/src/plugin.but index 8e2e2a45..961b6270 100644 --- a/Docs/src/plugin.but +++ b/Docs/src/plugin.but @@ -4,7 +4,7 @@ The abilities of the NSIS scripting language can be extended by utilising functi When the NSIS compiler starts it scans the plugins directory for DLLs and makes a list of the plugins found and their exported functions. During compilation if a sequence such as fred::flintstone is encountered where the compiler expected to find a language keyword the compiler will look through this list. If a list entry specifies that fred.dll exports function flintstone NSIS will pack the fred.dll file into the created installer binary. -During execution of the created installer if a plugin command is executed NSIS will unpack the necessary DLL to the $TEMP directory, execute the DLL function, then delete the DLL. If the /NOUNLOAD option is specified the DLL will not be deleted until the installer exits. +During execution of the created installer if a plugin command is executed NSIS will unpack the necessary DLL to the $TEMP directory, push all of the arguments specified (right-to-left order), and then execute the DLL function. If the /NOUNLOAD option is specified the DLL will not be deleted until the installer exits or the next time you use the DLL without /NOUNLOAD. \H{usingplug} Using Plugin Commands