Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/08/2017 in all areas

  1. SciTE Customization GUI is intended to be your one-stop solution for your SciTE customization needs. With SciTE Customization GUI you can create new themes from scratch without having to touch a single configuration file. Simply select 'Default Theme' from the file menu. This will start you out with a default theme. Then make your changes to the theme. Finally, select 'Save As' from the file menu and give it a name. Or you can select from an already existing theme. You can see live changes to SciTE as you change things around (some settings are not live). You can change various SciTE4AutoIt3 settings such as Tidy, Tools, debug trace messages, etc. I mostly want to try out new ideas which I hope will get used in the official SciTE4AutoIt3. I also wanted to see how large of a program I could script in AutoIt before it become a mass of unmaintable spaghetti. I feel that I am successful in that regard. It is reasonably easy to debug, extend and understand. I feel that this was achieved by employing the Model-View-Controller pattern. I also used AutoItObject which allows me to achieve a level of information hiding which would not have been possible otherwise. I stand on the shoulders of giants so credit where credit is due. Thanks to Jos for the original SciTEConfig. Thanks to Jon for AutoIt. Melba23 for the SciTE Abbreviation Manager and the SciTE UserCalltip Manager. Credits and changelog have be moved to the script. Note: this is not an official script. Jon, Jos or the rest of the AutoIt team do not provide support. That's all up to me. SciTE Customization GUI.zip -- downloads: ~5253 SciTE Customization GUI -- Source.zip -- Includes all of the required dependencies.
    1 point
  2. $Users = _AD_GetObjectsInOU("OU=Department,OU=Users,OU=topOU,DC=company,DC=local", "(&(objectcategory=person)(objectclass=user)(!userAccountControl:1.2.840.113556.1.4.803:=" & $ADS_UF_ACCOUNTDISABLE & "))")
    1 point
  3. Would it be sensible to create a CDO UDF similar to - lets say - the OutlookEX UDF? How many users would use it?
    1 point
  4. This work for me @LarsJ Global Const $S_OK = 0 Global $tCLSID_CLRMetaHost = _WinAPI_CLSIDFromString("{9280188d-0e8e-4867-b30c-7fa83884e8de}") Global $tIID_ICLRMetaHost = _WinAPI_CLSIDFromString("{D332DB9E-B9B3-4125-8207-A14884F53216}") Local $aRet = DllCall("MSCorEE.DLL", "long", "CLRCreateInstance", "struct*", $tCLSID_CLRMetaHost, _ "struct*", $tIID_ICLRMetaHost, "ptr*", 0) If $aRet[0] = $S_OK Then Local $pClrHost = $aRet[3] ConsoleWrite("$pClrHost: " & $pClrHost & @CRLF) EndIf Func _WinAPI_CLSIDFromString($sGUID) $tGUID = DllStructCreate('ulong Data1;ushort Data2;ushort Data3;byte Data4[8]') $iRet = DllCall('ole32.dll', 'uint', 'CLSIDFromString', 'wstr', $sGUID, 'ptr', DllStructGetPtr($tGUID)) If (@error) Or ($iRet[0]) Then Return SetError(@error, @extended, 0) EndIf Return $tGUID EndFunc ;==>_WinAPI_CLSIDFromString Saludos
    1 point
×
×
  • Create New...