ChiDragon

I'm setting a menu option using WinMenuSelectItem. But before I do that, I would really prefer to know the current state of the radio button options in that menu. My use case: I'm selecting a particular video capture card out of a list, and I want to query the list to make sure that it isn't already selected. This is because there is an annoying visual pause that takes place when "switching" between the cards, even if the change is to the exact same item. Is there a way to do this?

I'm trying to automate a standard menu in a program (VirtualDub) but I need to know the state of a checkmark on the menu in order to choose on-the-fly whether to use WinMenuSelectItem. If I use WinMenuSelectItem on it while it's already selected, it gets disabled and the checkmark is placed next to another item. Is there any way to check this status?

Whoops, guess I didn't refresh the page in between my edits. ShellExecute was actually the first command I tried before switching to Run and it likewise didn't work. As I said in my edit above, it was just a x86 vs x64 issue. Sure would be nice if Windows gave me some sort of error message instead of silently failing.

Yeah. Very confusing. Thanks for the feedback. EDIT: Even worse, I can't workaround it by running a cmd.exe window using AutoIt. If I try to type in the above commands into the launched window, the bthprops one triggers nothing but a quick flash of the spinning "busy" cursor. Again, the other one works. Both commands work from a cmd.exe launched by Windows' own Run dialog. I don't understand what the difference could possibly be. I even set the working directory to be the same. EDIT 2: Got it... 32-bit AutoIt launching 32-bit cmd.exe. For whatever reason I have to use the x64 version of AutoIt. All commands work then. Thanks.

I'm trying to automate Bluetooth device pairing and failing at the very first line, opening the Bluetooth Devices panel. Other panels open fine. Run ("control.exe bthprops.cpl") ; nothing Run ("control.exe timedate.cpl") ; opens Date and Time Both lines work when run from an ordinary command line, but I can't find any way to get bthprops to open from AutoIt. Running Windows 7 x64. Does the first run command work for anyone else?

Yep, .NET Framework 2.0 shows up in Add/Remove Programs and other .NET programs run fine if I'm not mistaken (I can't think of one I've got installed to test ATM).

I tried uninstalling and reinstalling them both multiple times and in different orders. I see the Wrapper DLL in the directory, and I am admin.

I get this error when I try to open any script including the Test one: The window title is AutoIt Debugger Wrapper. I noticed someone earlier in this thread had a similar problem that he fixed by installing the GUI package, but I already did that. Any idea what's going on?

Should I repost this in Bug Reports?

This is a forum, not a real-time chat.

I don't really understand what you're trying to do, but what about "If $ControlFocus <> $ButtonX"?

Where are you going to find a chat filled with people willing to be your bot-slaves at all hours?

Why do you want to declare it inside the If statement?

Something like this: Func _SearchArray (ByRef $aArray, $qString) For $x = 1 to UBound ($aArray) - 1 If StringInStr ($aArray[$x], $qString) <> "" Then Return $x ExitLoop EndIf Next Return 0 EndFunc $time_to_wait = 15 For $time_waited = 1 To $time_to_wait Sleep (1000) $process_list = ProcessList("rundll32.exe") For $i = 1 To $process_list[0][0] If _SearchArray ($ArrayPid, $process_list[$i][1]) = 0 Then If $debug = "Yes" Then _AddLineBox("DEBUG: Program found the process (" & $process_list[$i][1] & ") and now awaits for it to terminate.") ProcessWaitClose($process_list[$i][1]) _AddLineBox("System has now finished installing drivers for your hardware. Enjoy!") ExitLoop 2 EndIf Next If $time_waited = $time_to_wait Then _AddLineBox("No active plug & play process has been found after " & $time_to_wait & " seconds. Terminating.") EndIf Next There's probably a cleaner way to do the waiting loop but it's all I can think of at the moment.

I think if you do individual Cases for $nMsg it will perform the task each time the radio is clicked, rather than only after OK is pressed. You can either do Cases nested after the OK Case or Ifs nested after it. While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE Exit Case $Button1 If GUICtrlRead($Completed) = $GUI_CHECKED Then ... ElseIf GUICtrlRead($Attempted) = $GUI_CHECKED Then ... etc. EndIf Case $Button2 Exit EndSwitch WEnd