Timeline



Jul 27, 2018:

5:31 AM Ticket #1130 ($tagNMLVKEYDOWN stuct not working in x64 OS) updated by supersonic
It seems that this ticket still needs some attention. Using AutoIt V3.3.14.5 running in 64 bit $tagNMLVKEYDOWN (-> VKey) returns always 0. Please re-check :) For a solution/workaround please see: https://www.autoitscript.com/forum/topic/195016-lvn_keydowntagnmlvkeydown-does-not-work-in-64-bit/

Jul 20, 2018:

7:04 PM Ticket #3627 (Feature Request: AutoItWinGetHandle()) updated by BrewManNH
What exactly do you need the handle of the hidden window for? In 8 years of using AutoIt, I don't think I've ever seen anyone that ever needed that information, so I'm curious as to why you think this is necessary.

Jul 19, 2018:

8:23 AM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) closed by Melba23
No Bug
8:21 AM Ticket #3645 (StringRegExpSplit) closed by Melba23
Rejected
1:40 AM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) updated by jchd18
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 jchd18
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 genius257
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 Jos
Something like this? […] Jos
9:39 PM Ticket #3646 (unclosed comments start directive inside of comment section results in ...) created by genius257
The following code […] Results in […] Shouldn't anything …
11:28 AM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
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 Melba23
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 genius257 <hot415@…>
Well it seems i forgot the code block Here's the examples with the code block […]
5:05 PM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
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 therks
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 Melba23
You mean like this: […] M23
6:52 AM Ticket #3645 (StringRegExpSplit) updated by genius257 <hot415@…>
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 Jos
as in StringRegExp() you mean? Jos
9:12 PM Ticket #3645 (StringRegExpSplit) created by genius257 <hot415@…>
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 genius257 <hot415@…>
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 J-Paul Mesnage
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 TimRude <timrude@…>
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 BrewManNH
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.
Note: See TracTimeline for information about the timeline view.