Leaderboard

The AutoItX.chm is a separate helpfile located in its subdirectory and doesn't have the -1 to -4 option.

In any case, it didn't work either way for me. And I've already migrated to System.Diagnostics.

Hi GianniTrattore, As Melba23 didn't lock the thread then I guess advices can be given. Send($vLink) is not instantaneous, you should try to replace it with : ClipPut($vLink) Send("^v") ; Ctrl+V, much faster than Send($vLink) I noticed that when I faced a similar situation like yours (to automatically fill the adress bar with an URL) Hope it will work for you.

The message handling techniques that you mention in the first section can only be used in your own applications where you write the code yourself. These techniques are used in programming areas that can generally be termed as user interface development (UI development). The techniques can only be used when you write the code yourself. There are generally two techniques for interacting with external applications: automation and hooking techniques. The hooking technique assumes that the associated message handler function is implemented in a dll-file. However, dll-files cannot be created using the AutoIt language. So the only real option is the automation techniques. An example where the automation technique is used to add an additional menu item to the Notepad context menu and then detect that the menu item is clicked is found here. May be this method can also be used for the window system menu.

We finally found a solution that worked just by continuing to test different options. In case this helps anyone else, here is what we found that finally worked. $sConnStr = "Provider=SQLNCLI11;SERVER=servername,port;DATABASE=dbname;DataTypeCompatibility=80;UID=user;PWD=pass"

Hi UE_morf_boon It will work with the correct syntax (tested on MetroUDF example) : GUICtrlSetState(-1, $GUI_HIDE)

Are you playing with the handles of your....coffin ?

You owe me a beer for this #include <Constants.au3> #include <Process.au3> #include <WinAPISysWin.au3> #include <WinAPIProc.au3> #include <Array.au3> Opt("MustDeclareVars", 1) Local $aPrograms[0][4] Local $aWinList = WinList() Local $iPID, $sName For $i = 1 To $aWinList[0][0] If $aWinList[$i][0] <> "" And BitAND(WinGetState($aWinList[$i][1]), 2) Then $iPID = WinGetProcess($aWinList[$i][1]) $sName = _ProcessGetName($iPID) If $sName = "ApplicationFrameHost.exe" Then $iPID = FindTrueApp($aWinList[$i][0], $iPID, $sName) If Not $iPID Then ContinueLoop EndIf _ArrayAdd($aPrograms, $aWinList[$i][0] & "|" & $aWinList[$i][1] & "|" & $iPID & "|" & $sName) EndIf Next _ArrayDisplay($aPrograms) Func FindTrueApp($sTitle, $iPID, ByRef $sProcess) Local Static $aList = _WinAPI_EnumWindows(True) Local $iTruePID For $i = 1 To $aList[0][0] If WinGetTitle($aList[$i][0]) = $sTitle Then $iTruePID = WinGetProcess($aList[$i][0]) If $iPID <> $iTruePID Then $sProcess = _WinAPI_GetProcessName($iTruePID) Return $iTruePID EndIf EndIf Next Return 0 EndFunc ;==>FindTrueApp Working nicely for me...

Have you check out _WD_UpdateDriver in wd_helper.au3? I haven't examined your code, but I imagine they are performing similar actions.