We can use AutoIt within a KiX script as well. In fact, the two complement each other nicely. KiX can do many things that AutoIt cannot. AutoIt handles "windows" better. Here's a sample of using the AutoItX.dll:

code:
; Check for and install AutoItX.dll if not present.
if exist("%windir%\autoitx.dll")=0
	copy "@scriptdir\autoitx.dll" "%windir%"
	shell "regsvr32 /s %windir%\autoitx.dll"
endif
$oAutoIt = CreateObject("AutoItX.Control")
if $oAutoIt=0
	? "AutoItX not registered."
endif
; Pause script until "Version Conflict" window exists.
; Then send an ALT-Y to confirm "Keep existing driver."
$=$oAutoIt.WinWaitActive ("Version Conflict","",0)
	$=sendkeys("~Y")
As mentioned, this script would have to be running concurrently with the execution of another script. This "Adlib" example would just be sitting there waiting until the proper condition existed. Probably not the best example in the world, as it would stay paused until that window popped up. It would be better to do a "IfWinExist." You could then have the "Adlib" loop as long as Outlook (or Notes in this case) is open. Then, once Outlook is closed, the "Adlib" script exits.