Leaderboard

another flavour StringRegExp($txt,"(?:start|end)(*SKIP)(*F)|\b(\w+)\b", 3)

Place $CF_UNICODETEXT first to keep away of unwanted conversion.

I update for: Local $aReg=StringRegExp($String,"\b(?!(end|start))\w+\b",3) Work fine. Thank you @Danyfirex

try this: Local $aReg=StringRegExp($String,"\b(?!(end|start))[0-9a-z]{1,}\b",3) Saludos

Examples (The query needs the latest version of the UDF (1.2.1.0) which I'm going to release quite soon): ; Enable/Disable the Registered Task Global $aProperties[] = ["TASK|Enabled|xxxx"] ; Replace xxxx with True or False to enable or disable the task _TS_TaskPropertiesSet($oTask, $aProperties) ; Query the Registered Task $aTaskProperties = _TS_TaskPropertiesGet($oService, $oTask, 1, False, "TASK", "Enabled") MsgBox(0, "Query Task", "Task is enabled = " & $aTaskproperties[0][2])

That's what I meant. One side is Global, the other Local and Dim is the bridge that covers both. When saying "bad style", I mean it's much less clear than using either Global or Local, unless the (rare) only use case I mentionned.

At a command prompt, use absolute paths and see if it works. For example: C:\> "C:\Program Files\AutoIt3\autoit3.exe" <path to your au3 file>

Likewise.

please ignore my previous question on COM error 80020009. i have answered my own question (as to what might be wrong and how to troubleshoot): it turned out that on this particular system my performance counter registry was corrupt! i was also getting errors when running "perfmon.msc". eventually i solved it by following the steps in https://support.microsoft.com/en-us/kb/2554336 : open an elevated command promptCD /D C:\windows\system32lodctr.exe /RCD /D C:\windows\sysWOW64lodctr.exe /RWINMGMT.EXE /RESYNCPERF<reboot>

Use StringSplit. ; #include <Array.au3> Local $sString = "", $iMax = 10, $sDelim = "," For $i = 1 To $iMax $sString &= "test" & $i & $sDelim Next $sString = StringTrimRight($sString, 1) Local $aArray = StringSplit($sString, $sDelim, 2) _ArrayDisplay($aArray)

In addition to what Hannes said: The Scite console is quite smart to figure that you want a single line break in all cases you tested. Most recent and all decent text editors allow you to use any line break combination. BUT you need to check the other applications which will be using the text files you produce or modify and verify they don't behave unexpectedly when they encounter line-terminations distinct from what they expect. As a general rule of thumb, Hannes advice to stick with @CRLF in Windows context is a safe bet. FYI those names come from the times when typewriter devices (Google for LA36 for instance) were used before CRT terminals appeared (and long after them!). CR meant exactly that: make the print head return to home (leftmost position) and LF caused the paper to advance one line, without moving the print head. So the combination of both was actually required to skip to the home position of a new line. The operator however never had to hit two keys to do that, just hit Return, which was internally translated into either LF or CR (depending on the underlying system) and understood by the terminal driver as a request to "print" CRLF.

@rkskaras The format of DesiredCapabilities is obviously incorrect. I gave a shot at assisting you to fix it, but obviously I was wrong. Let us know if you come up with a working example.