Timeline
Jul 19, 2018:
- 8:23 AM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) closed by
- No Bug
- 8:21 AM Ticket #3645 (StringRegExpSplit) closed by
- Rejected
- 1:40 AM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) updated by
- It seems #cs & #ce somehow nest: it appears you need as many #ce as #cs. If you have one more of any of #cs or #ce, the interpretor barks. Here it complains about "extra": […] I wouldn't qualify this behavior as "bug": say "feature".
- 1:27 AM Ticket #3645 (StringRegExpSplit) updated by
- It can still work: […] But maybe you'll tell us that if the subject has adjacent separators it won't again work the way you expect it to. Note that since the function is an actual one-liner, there is no real purpose for a new function: it's simpler to code it inline with the ad-hoc pattern suited to the case being handled. Also Trac isn't the place to discuss various regexes; better post a topic in help and when & if a new function emerges from discussion then it'll be time to place a feature request here.
- 1:03 AM Ticket #3645 (StringRegExpSplit) updated by
- Hmmm seems to work for almost everything, except the following. […] But the chances for that to give me problems currently are slim :)
Jul 18, 2018:
- 10:59 PM Ticket #3645 (StringRegExpSplit) updated by
- Something like this? […] Jos
- 9:39 PM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) created by
- The following code […] Results in […] Shouldn't anything …
- 11:28 AM Ticket #3645 (StringRegExpSplit) updated by
- Yeah, the last one was meant to be […] And i do get that StringRegExp CAN solve this, it simply seems like a ease of use function. Especially when converting from one language (like js or php) to AutoIt
- 9:40 AM Ticket #3645 (StringRegExpSplit) updated by
- The first 2 are easy to do with the existing function: […] No idea about the last one as the given input does not match the required output in any way. M23
Jul 17, 2018:
- 5:09 PM Ticket #3645 (StringRegExpSplit) updated by
- Well it seems i forgot the code block Here's the examples with the code block […]
- 5:05 PM Ticket #3645 (StringRegExpSplit) updated by
- In a small, simple example, yes. StringRegExpSplit("|a|| |b|| c| ||d|", "\s*\|\|\s*") [ "|a", "|b", "c|", "d|" ] Or StringRegExpSplit("|a|| |b|| c| ||d|", "\s*(\|\|)\s*") [ "|a", "||", "|b", "||", "c|", "||", "d|" ] Or StringRegExpSplit("Hello 1 word. Sentence number 2.", "(\d)") [ "Hello ", "1", " word. Sentence number ", "2", "." ]
- 1:47 PM Ticket #3627 (Feature Request: AutoItWinGetHandle()) updated by
- I suppose if that variable is set and used like a constant (at the beginning of a script launch), there would probably be no problems. But if the lookup for the window handle happens some time after launch (eg: from a UDF) when the calling process is not focused, it could return the incorrect handle. For example, if you have a folder open titled "AutoIt v3" and your script calls WinGetHandle(AutoItWinGetTitle()) a few minutes after it was first launched, it will return the Explorer window. Maybe it would even be more appropriate as a macro, like @AutoItWinHandle. I guess it doesn't matter though as it seems I'm the only one interested.
- 10:34 AM Ticket #3645 (StringRegExpSplit) updated by
- You mean like this: […] M23
- 6:52 AM Ticket #3645 (StringRegExpSplit) updated by
- Yes and no. Yes that it's by using regular expression. No because StringRegExp returns the part of string matched by the pattern. For example StringRegExpSplit("abc", "(:?)") would return ["a", "b", "c"]
Jul 16, 2018:
- 9:16 PM Ticket #3645 (StringRegExpSplit) updated by
- as in StringRegExp() you mean? Jos
- 9:12 PM Ticket #3645 (StringRegExpSplit) created by
- A core function to split strings by regular expression.
Jul 15, 2018:
- 10:06 PM Ticket #3560 (parentheses around function refference fails when follwed by calling ...) updated by
- Hi Jos :) I've tried the au3check.exe from the autoit-v3.3.15.1.zip of the beta download, and i still seem to get the same problem. Sorry for the slow response, i have tried adding my mail my preferences in hope that i will get a notification when there's responses in a ticket i participate in :) […]
Jul 5, 2018:
- 7:45 AM Ticket #3642 (AutoItX/ControlTreeView - wrong example in HelpFile) closed by
- Fixed: Fixed by revision [12160] in version: 3.3.15.1
Jul 4, 2018:
- 9:52 PM Ticket #3641 (Allow ProgressOn function to return window handle of the progress ...) updated by
- Yes, it is fairly simple to get the handle of it using something like WinGetHandle("[TITLE:blah blah blah; CLASS:AutoIt v3]"). But what would be the harm of having the function call simply return the handle of the dialog? Then you wouldn't have to futz around with looking for the window, making sure in code that you update the title text in the WinGetHandle call if you update it in the ProgressOn call, or wonder if maybe there's another AutoIt process that spawned a progress dialog with the same title (unlikely, but not entirely impossible). Since there's currently no return value from the ProgressOn function, this would be a useful addition with no negative impact on existing code whatsoever.
Jul 2, 2018:
- 5:28 PM Ticket #3641 (Allow ProgressOn function to return window handle of the progress ...) updated by
- The ProgressOn function is a very basic splash screen with progress bar. Getting the handle of it should be simple enough, or you could just build your own so you have absolute control over it. There are examples in the forum of DIY splash screens with progress bars.
Jun 30, 2018:
- 11:51 AM Ticket #3643 (For...To...Step...Next - variable is NOT (see Remarks in AutoIt Help) ...) closed by
- No Bug
- 8:24 AM Ticket #3644 (ArrayDisplayInternals.au3 - used magic numbers as constants) closed by
- No Bug: As I want to minimize #include and those function are internal duplication the magic number is not used
Jun 29, 2018:
- 12:08 PM Ticket #3643 (For...To...Step...Next - variable is NOT (see Remarks in AutoIt Help) ...) updated by
- This is how it is described in the Helpfile under: AutoIt/Language Reference/Variables and look for the paragraph Scope: =========================================================================================== Scope A variable's scope is controlled by when and how you declare the variable. If you declare a variable at the start of your script and outside any functions it exists in the global scope and can be read or changed from anywhere in the script. If you declare a variable inside a function it is in local scope and can only be used within that same function. Variables created inside functions are automatically destroyed when the function ends. By default when variables are declared using Dim or assigned in a function they have local scope unless there is a global variable of the same name (in which case the global variable is reused). This can be altered by using the Local and Global keywords to declare variables and force the scope you want. See Static for details on how to use this keyword as part of the scope declaration. ============================================================================================ Hope that explains it. Jos
- 9:31 AM Ticket #3644 (ArrayDisplayInternals.au3 - used magic numbers as constants) created by
- In ArrayDisplayInternals.au3 UDF are used magic numbers as constants …
- 1:47 AM Ticket #3643 (For...To...Step...Next - variable is NOT (see Remarks in AutoIt Help) ...) updated by
- Ok, better I would have said it's not an error ... but that the text under Remarks leads to assumption that $i would be in the Local scope anyway. The trigger for my ticket was the Notify UDF by Melba23 ... line 47-49. […]
Jun 28, 2018:
- 6:44 PM Ticket #3643 (For...To...Step...Next - variable is NOT (see Remarks in AutoIt Help) ...) updated by
- Any variable in the main part of the script is global. Try this version to see what i mean: […] So this is as designed and no bug. Jos
- 4:17 PM Ticket #3643 (For...To...Step...Next - variable is NOT (see Remarks in AutoIt Help) ...) created by
- […]
- 11:44 AM Ticket #3642 (AutoItX/ControlTreeView - wrong example in HelpFile) created by
- AutoItX/ControlTreeView --> example in HelpFile is missing and …
Jun 27, 2018:
- 7:52 PM Ticket #3641 (Allow ProgressOn function to return window handle of the progress ...) created by
- Presently, the ProgressOn function has no return value. It would be …
Jun 23, 2018:
- 8:28 AM Ticket #3640 (Bug sound Windows 10 x64 with Scite) closed by
- No Bug: You have already posted in the forum asking about this - wait until you get a reply before suggesting there is a bug. M23
Jun 22, 2018:
- 10:11 PM Ticket #3640 (Bug sound Windows 10 x64 with Scite) created by
- (Google Translator) When I run an audio through SciTe, windows 10 x64 …
Note:
See TracTimeline
for information about the timeline view.
