FCT plug-in: Difference between revisions
No edit summary |
No edit summary |
||
Line 14: | Line 14: | ||
=== "fct" DLL function === | === "fct" DLL function === | ||
<highlight-nsis> | <highlight-nsis> | ||
fct::fct [/NOUNLOAD] [/WC CLASS | /WCP CLASS_PART] [/WT WINDOW_TITLE | /WTP TITLE_PART] [/ASYNC] [/TIMEOUT xxx] [/UDATA xxx] /QUESTION TERM_QUEST [/END] | fct::fct [/NOUNLOAD] [/WC CLASS | /WCP CLASS_PART] [/WT WINDOW_TITLE | /WTP TITLE_PART] [/ASYNC] [/TIMEOUT xxx] [/UDATA xxx] [/QUESTION TERM_QUEST] [/END] | ||
</highlight-nsis> | </highlight-nsis> | ||
: Searchs for all windows with predefined 'class' and 'title' (or it's part if /WCP or /WTP keys used). In async mode plug-in returns running terminator thread handle, in the sync one - still alive applications count (i.e. how many application not exited after WM_CLOSE and were not terminated using TerminateProcess() ). Returnes "-1" if /QUESTION was defined, application not exited after WM_CLOSE and user selected Cancel on the MessageBox. I.e. 0 is OK. Use 'wait' with handle as parameter to get final result for async mode. | : Searchs for all windows with predefined 'class' and 'title' (or it's part if /WCP or /WTP keys used). In async mode plug-in returns running terminator thread handle, in the sync one - still alive applications count (i.e. how many application not exited after WM_CLOSE and were not terminated using TerminateProcess() ). Returnes "-1" if /QUESTION was defined, application not exited after WM_CLOSE and user selected Cancel on the MessageBox. I.e. 0 is OK. Use 'wait' with handle as parameter to get final result for async mode. |
Revision as of 13:46, 13 January 2006
Author: Takhir (talk, contrib) |
"FCT" stands for "Find and Close or Terminate".
Links
Download:
Fct.zip (8 KB)
Description
Plug-in terminates application in 2 steps - first send WM_CLOSE to it's main window, then (if still alive) terminates application. Has sync/async (background) modes, async is good for slowly exiting applications (maximum delay for one application may be up to 2xTIMEOUT) and multiple applications (multithreading). Plug-in closes or terminates all process with top level windows of such kind using EnumWindows(). Never closes installer $HWNDPARENT. Size is 2 kB in zip, so if you need WIN API calls for correct process termination only, this may replace System plug-in with less size and simple script code. Final package size is 4 kB less in compressed file for installer only and 8 kB if it replaces System plug-in both in installer and uninstaller.
Syntax
"fct" DLL function
fct::fct [/NOUNLOAD] [/WC CLASS | /WCP CLASS_PART] [/WT WINDOW_TITLE | /WTP TITLE_PART] [/ASYNC] [/TIMEOUT xxx] [/UDATA xxx] [/QUESTION TERM_QUEST] [/END]
- Searchs for all windows with predefined 'class' and 'title' (or it's part if /WCP or /WTP keys used). In async mode plug-in returns running terminator thread handle, in the sync one - still alive applications count (i.e. how many application not exited after WM_CLOSE and were not terminated using TerminateProcess() ). Returnes "-1" if /QUESTION was defined, application not exited after WM_CLOSE and user selected Cancel on the MessageBox. I.e. 0 is OK. Use 'wait' with handle as parameter to get final result for async mode.
- WT
- WINDOW_TITLE is a full window title
- WTP
- TITLE_PART is only a part of window title (caption)
- WC
- WINDOW_CLASS is a full window class name
- WTP
- CLASS_PART is only a part of window class name
- ASYNC
- Not waits for process exit. Use 'wait' call if you want to get result
- TIMEOUT
- timeout for SendMessage() and WaitForSingleObject(). Default is 1000 (ms).
- UDATA
- if few applications have "32770" class based windows and all titles include only a fragment of TITLEPART, situation becomes confusing. This case developer can preset specific GWL_USERDATA value to his app's window, plug-in will check, for example, /udata=0x12fe3400.
- QUESTION
- TERM_QUEST - text to display on the MessageBox if application not exited on WM_CLOSE. Skipped in the Silent mode.
"wait" DLL function
fct::wait handle
- Waits for terminator thread exit in async mode.
- handle
- Control thread handle returned by 'fct' call in the /ASYNC mode.
Example
Sync execution:
fct::fct /WC '${WND_CLASS}' /WTP '${MY_TITLE}' /TIMEOUT 2000 /QUESTION 'Terminate?' Pop $0 StrCmp $0 "-1" 0 +2 Abort "Terminated by user" MessageBox MB_OK "Still Alive Count=$0"
Async execution:
fct::fct /NOUNLOAD /WC '${WND_CLASS}' /ASYNC ; You can place some code here. We skipped Pop and Push for hThread - it just sits in the stack. 'Question' not defined - silent execution. fct::wait Pop $0 MessageBox MB_OK "Still Alive Count=$0"