Leaderboard

A custom property must be implemented by the provider of the application before it can be used by the client. A client cannot create a custom property. This method does not seem to be a solution. If you can disable the button manually, you can probably automate the process too. A button is usually supplied with an enabled property ($UIA_IsEnabledPropertyId). You can use the Spy tool or Inspect.exe to figure out, if you can set the value ($UIA_ValuePatternId) of this property.

Try $hWnd = _IEPropertyGet($oIE, "hwnd")Also, I would not advise to declare scope (Global or Local) in a loop, it wont break your script, but it's not usual protocol.

Dell is shipping new laptops with a root cert called "eDellRoot". Same Cert on every box, not unlike superfish. https://www.reddit.com/r/technology/comments/3twmfv/dell_ships_laptops_with_rogue_root_ca_exactly/

Performance update. See last part of the first post.

this snippet; Case $idDummy Switch GUICtrlRead($tab) Case 0 _GUICtrlButton_Click($idButton_1) Case 1 _GUICtrlButton_Click($idButton_2) EndSwitch EndSwitch can be like this: Case $idDummy _GUICtrlButton_Click($idButton_1) _GUICtrlButton_Click($idButton_2) EndSwitch But if you want really click both button on different TabItem then you must use GuiSwitch like this: #include <GUIConstantsEx.au3> #include <StaticConstants.au3> #include <WindowsConstants.au3> #include <GuiButton.au3> _Example() Func _Example() Local $hGUI = GUICreate("My GUI Tab", 210, 110) ; will create a dialog box that when displayed is centered Local $idDummy = GUICtrlCreateDummy() $tab = GUICtrlCreateTab(10, 10, 200, 100) Local $idTabItem_1 = GUICtrlCreateTabItem("tab 1") Local $idButton_1 = GUICtrlCreateButton("Tab 1", 20, 50, 50, 20) Local $idTabItem_2 = GUICtrlCreateTabItem("tab 2") GUICtrlSetState(-1, $GUI_SHOW) ; will be display first Local $idButton_2 = GUICtrlCreateButton("Tab 2", 140, 50, 50) GUICtrlCreateTabItem(""); end tabitem definition Local $aAccelKeys[1][2] = [["{Enter}", $idDummy]] GUISetAccelerators($aAccelKeys) GUISetState(@SW_SHOW) Local $idMsg ; Loop until the user exits. Local $idActiveTabItem While 1 ; You can not click $idButton_1 when Tab2 is active ; I think this is normal Windows GUI behavior ;_GUICtrlButton_Click($idButton_1) Switch GUIGetMsg() Case $GUI_EVENT_CLOSE ExitLoop Case $idButton_1 MsgBox(0, 'Test', "But1") Case $idButton_2 MsgBox(0, 'Test', "But2") Case $idDummy $idActiveTabItem = GUICtrlRead($tab) Switch $idActiveTabItem Case 0 _GUICtrlButton_Click($idButton_1) GUISwitch($hGUI ,$idTabItem_2) _GUICtrlButton_Click($idButton_2) Case 1 _GUICtrlButton_Click($idButton_2) GUISwitch($hGUI ,$idTabItem_1) _GUICtrlButton_Click($idButton_1) EndSwitch GUISwitch($hGUI ,$idActiveTabItem) EndSwitch WEnd EndFunc ;==>_Example

http://superuser.com/questions/767286/re-enable-extensions-not-coming-from-chrome-web-store-on-chrome-v35-with-enhan Download the crx file and unpack the extension using your favorite decompresser. Take note of the directory where you placed it.Open the extension page, activate "Developer Mode"Click "Load unpacked extension..."Search trough your directory tree for the directory where you unpacked your extension and click OK. If your extension is called "my extension" then select "my extension" directory.Advantages: You don't have to install anything else. Disadvantages: Chrome nags you to disable the extension each start up. I've tried this with Chrome 48, it keeps the extension enabled, but pops up a dialog if you want to disable it or cancel. The other option is to whitelist the extension with the Windows policy editor: https://productforums.google.com/forum/#!msg/chrome/9NlMAr6uEVc/ambkrcKpi1cJ This doesn't bother you with a popup every time you start Chrome.