Timeline

View changes from
going back days
by author

Milestones completed Tickets opened and closed Ticket updates Wiki changes

Apr 10, 2015:

4:19 AM Ticket #3011 (_FileListToArrayRec does not closes file handle) updated by MrCreatoR <mscreator@…>

Yes, 3.3.13.20 returns 0, but the UDF should be changed, FindFirstFileW handle never closed. […] should be […]

Apr 6, 2015:

4:34 PM Ticket #3011 (_FileListToArrayRec does not closes file handle) updated by Melba23

When running that reproducer script with 3.3.12.0, the second MsgBox indeed displays "1, 1" - running with 3.3.13.20 it displays "0, 0". Can you confirm? M23

Apr 5, 2015:

9:40 AM Ticket #3011 (_FileListToArrayRec does not closes file handle) created by MrCreatoR <mscreator@…>

After we read files in subfolders, the folder handle is not closed, …

Apr 2, 2015:

5:37 PM Ticket #3010 (Au3Info - Double Click on Listview in "Control" Tab) created by mLipok

When I 2*click on "Advanced Mode" then I get "[CLASS:Button; …

Apr 1, 2015:

10:48 AM Bad Hand MouseGetCursor.png attached to Ticket #3009 by J-Paul Mesnage

10:48 AM Ticket #3009 (MouseGetCursor for HAND) created by J-Paul Mesnage

Running GUISetCursor examle and after run MouseGetCursor example does …

Mar 30, 2015:

6:23 PM Ticket #3008 (texting on a notepad) closed by Jos

Rejected: This is a site for feature requests or Bug reports, not support requests. Please visit our forum for support. Jos

12:00 PM Ticket #3008 (texting on a notepad) updated by TicketCleanup

Version changed
Automatic ticket cleanup.

11:11 AM Ticket #3008 (texting on a notepad) created by maheshit22@…

I am able to enter text in a notepad and save it. But what 1.if i …

Mar 28, 2015:

10:16 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) updated by anonymous

@BrewManNH : you pointed exatly what I was trying to do to assist a forum user in this thread : ​http://www.autoitscript.com/forum/topic/169135-flexibility-with-declaring-an-array/ I wanted to post this kind of code : […] But when I saw the result, I decided to write a ticket here. For me, it is a bug, but you decid :-) If not, maybe something about this "bad" uasge should appear in the help file

8:22 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) updated by BrewManNH

You're calling the function to get the returned value for the array assignment, then you're calling it again when you actually set the value to the array. Run this modification to your code to see what's happening. […] It calls the function the first time to see what element of the array to set it to, then when AutoIt does the actual declaration for the element it calls it again to see where it's going. You'll notice that the only element with anything in it is $aArray[1] because that's what the return value is when you set the string to the array. So, I don't know if this is a bug, but it looks like a bad idea to use a function call to determine where in an array to put something, at least don't do it in the actual declaration statement, because you won't be able to be 100% sure it's going where you think it's going.

Mar 26, 2015:

10:19 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) updated by jguinch

I don't really understand what you mean in comment3…

5:15 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) updated by anonymous

Replying to Melba23: > Interesting that it does not do the same when you set the function to a variable Not very interesting. You assign the return value of the function to a variable and then evaluate that variable expression (twice).

4:44 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) updated by Melba23

Interesting that it does not do the same when you set the function to a variable: […] M23

3:42 PM Ticket #3007 (Make {} the empty map.) created by Jaberwacky

[…]

3:41 PM Ticket #3006 (Create a shortcut for the expression in a With statement.) created by Jaberwocky

[…]

3:39 PM Ticket #3005 (Allow maps as expressions in a "With" statement.) created by Jaberwacky

[…]

12:29 PM Ticket #3004 (Anonymous Maps) updated by jaberwacky

OK, it occurred to me just now. Should I create three separate trac tickets for these proposals? I still think these three proposals do not cover my original feature request though. I was hoping to set up an anonymous map using With and then refer to the map accordingly. However, the syntax for the empty map did always seem somewhat wrong though. […] Is this a better syntax?

Mar 25, 2015:

11:08 PM Ticket #3004 (Anonymous Maps) updated by anonymous

OK, everything is clear now. Thank you clearing that up. Now that I've reread your posts with my refreshed perspective, I agree with all points.

10:45 PM Ticket #3004 (Anonymous Maps) updated by anonymous

Replying to jaberwacky: > I'm not exactly sure what you're saying with proposal 2 and 3. I'm saying that you're proposing three different things and that they should be considered separately. > Are you saying the idea is good but that the execution is bad? I think there were some problems and suggested possible refinements. Personally I support all three proposals. Replying to anonymous: > How does this make the language inconsistent? This only applies to maps and not arrays and not objects. Dot access does not imply object object orientation. I'm actually not trying to subtly sneak anything OO related into the language. I didn't even think about objects, they're a lost cause. I think that it's a bad idea to use one syntax for two different things: array and map creation. I don't like the current way to create a map: Local $map[] I'd prefer Local $map = {} or Local $map = Map () or Local $map = NewMap () or Local $map = @EmptyMap because they make it clear what is happening. But [] does not. Why should Local $array = [] (array initialization) and Local $map = ([]) (empty map expression) create different things?

4:51 PM Ticket #3004 (Anonymous Maps) updated by anonymous

Rewind... How does this make the language inconsistent? This only applies to maps and not arrays and not objects. Dot access does not imply object object orientation. I'm actually not trying to subtly sneak anything OO related into the language.

4:22 PM Ticket #3004 (Anonymous Maps) updated by jaberwacky

Replying to anonymous: > It makes AutoIt inconsistent and is not open for extensions. > Why not @EmptyMap? I'm not exactly sure what you're saying with proposal 2 and 3. Are you saying the idea is good but that the execution is bad? @EmptyMap Works for me.

1:22 PM Ticket #2831 (Function Binding) updated by anonymous

Replying to jchd18: This was closed because of a misunderstanding, please reopen.

1:13 PM Ticket #3004 (Anonymous Maps) updated by anonymous

Replying to jaberwacky: > As far as I know AutoIt isn't trying to mimic or make it easy for JS, PHP, etc programmers. I'm sure all languages have their syntax differences that all people new to the language would have to learn. If someone coming to AutoIt from another language tries to use AutoIt the same way they used their previous language, that is an operator error. It makes AutoIt inconsistent and is not open for extensions. Why not @EmptyMap?

5:21 AM Ticket #3004 (Anonymous Maps) updated by anonymous

Sorry for the double post.

5:20 AM Ticket #3004 (Anonymous Maps) updated by jaberwacky

As far as I know AutoIt isn't trying to mimic or make it easy for JS, PHP, etc programmers. I'm sure all languages have their syntax differences that all people new to the language would have to learn. If someone coming to AutoIt from another language tries to use AutoIt the same way they used their previous language, that is an operator error.

5:19 AM Ticket #3004 (Anonymous Maps) updated by jaberwacky

As far as I know AutoIt isn't trying to mimic or make it easy for JS, PHP, etc programmers. I'm sure all languages have their syntax differences that all people new to the language would have to learn. If someone coming to AutoIt from another language tries to use AutoIt the same way they used their previous language, that is an operator error.

12:41 AM Ticket #3004 (Anonymous Maps) updated by anonymous

This actually contains three proposals: 1. Allow maps as expressions in a "With" statement. Example: […] Maps and "Object-type variables" have the same syntax. That extension is only natural. 2. Create a shortcut for the expression in a With statement. Example: […] What about ..element? Saves at most one line, not intuitive, easy to miss, will confuse programmers and tools, strange semantics, might encourage overuse – probably a bad idea, but absolutely possible. [] is a bad idea, see point 3. .[] is really strange, probably hard to implement and makes you assume that $object is a map, althrough it may be an "Object-type variable". Maybe with an additional keyword or constant (@WithExpression). 3. Make [] the empty map. Example: […] Note that the parentheses in the third-last line are a necessary syntactic disambiguation. Without them, it would be a broken array initialization (see #2845), or ambiguous. The same is true for 2d array initializations. Again, this may save at most one line. It will confuse any programmer coming from any language where that is an expression for an empty array (JS, PHP, ...): they will use it thinking that it is an empty array, and will be legitimately surprised when their program breaks. Definitely a bad idea. Maybe with braces ({})?

Mar 24, 2015:

10:12 PM Ticket #3004 (Anonymous Maps) created by jaberwacky

So I have an idea which I think will make coding a little easier in …

12:38 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) updated by jguinch

Also, this code is a good example of what happends : […]

Mar 23, 2015:

10:58 PM Ticket #3003 (Using a function call in an array assignment causes 2 function calls) created by jguinch

With this code : […] "myFunction" appears two times in the output …

Mar 22, 2015:

5:22 PM Ticket #2988 (_Excel_RangeFind fails without throwing error when searching inactive ...) updated by water

Fixed by revision [11253] in version: 3.3.13.21

5:21 PM Ticket #2988 (_Excel_RangeFind fails without throwing error when searching inactive ...) closed by water

Fixed: Fixed by revision [11252] in version: 3.3.13.21

5:07 PM Ticket #2993 (_Excel_RangeFind returns only last occurrence of string found Rather ...) closed by water

Fixed: Fixed by revision [11251] in version: 3.3.13.21

11:52 AM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') updated by jchd18

Oops, I never read the help file down to the last Remark line. BTW, this important remark about allowable date formats would be better placed in the $Date parameter description: "Input date in the format YYYY/MM/DD[ HH:MM:SS]" --> "Input date in any format described in _DateTimeSplit()". Sorry for the noise, but yes I still find it would be natural to expect the function to return dates under the same format used for input.

2:23 AM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') updated by guinness

jchd, It does accept - (see the StringSplit() in _DateTimeSplit() […] Unless you meant the output should be 2015-03-21 00:00:01 and not 2015/03/21 00:00:00

2:15 AM Ticket #2983 (_WinApi_GetString documentation error) closed by guinness

Fixed

Mar 21, 2015:

10:38 AM Milestone 3.3.13.20 completed

4:35 AM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') updated by jchd

I'm not sure this qualifies as 'bug' and I'd rather see this as a feature request, for when you supply a date only (without time), that doesn't always imply that you mean time = '00:00:00'. Yet commonly used library functions work the way to want and consider a default time part to be '00:00:00'. BTW if ever this is accepted, I'd like other would also consider another modification. Currently the function only works when the date separator is a slash (/), but the standard separator specified by ISO 8601 is a dash (-). It would be pretty beneficial to simply mask off the separator in the regexp, yet take care to use the same separator in output. […] The same change should be made to related _Date* functions, like _DateDiff and some others. The best witness that this change is indeed needed is that _DateIsValid accepts both separators! Note: I don't advocate to accept any more format variant described in ISO 8601.

Mar 20, 2015:

2:14 PM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') updated by mLipok

Modyfication I mean only by appropriate use this new internal function.

2:12 PM Ticket #3002 (Bug - _DateAdd('s', 1, '1970/01/01') Returns '1970/01/01') created by mLipok

Repro: […] solusion proposal: new internal function: […] …

Mar 19, 2015:

2:24 PM Image 028.png attached to Ticket #2481 by anonymous

Don't seen initial dir path in the dialog.

Mar 13, 2015:

5:29 PM Ticket #3000 (scriptline) updated by anonymous

Ok nevermind, looks like custom error handling won't be useful for me anyway. For me it returns -1, are you sure it is compiled script?

Mar 12, 2015:

2:03 PM Ticket #2988 (_Excel_RangeFind fails without throwing error when searching inactive ...) updated by water

Owner, Status changed

2:03 PM Ticket #2993 (_Excel_RangeFind returns only last occurrence of string found Rather ...) updated by water

Owner, Status changed

2:01 PM Ticket #2993 (_Excel_RangeFind returns only last occurrence of string found Rather ...) updated by water

The problem was caused by exiting the loop to search in the next sheet before increasing the index. Thus the first hit of the next sheet was overwriting the last hit of the previous sheet. This should work as well. Can you please confirm? […]

12:11 PM Ticket #2994 (Can't run _Excel_RangeFind example in 3.3.13.19) closed by water

Wont Fix: This is caused by the way AutoIt 3.3.13.19 handles COM errors. Up to 3.3.12.0 a COM error was returned by setting @error, with 3.3.13.19 the script crashes when you haven't set up a COM error handler. Up to 3.3.12.0 the script simply checked @error and then decided what to do. Now you need a COM error handler even when you wanted to ignore the error. I hope this change will be thought over before the release of the next production version. Now it is a huge overhead with little to none advantage compared to the "old" solution. The current Excel UDF in the repository has a COM error handler established for each function when called and dropped at the end.

9:04 AM Ticket #3000 (scriptline) updated by mLipok

in […] I use example from HelpFile and in Au3.3.10.2 and Au3.3.13.19 I get: […] And in helpFile you can read: @ScriptLineNumber Line number currently being executed. Useful for debug statements such as the calling line number for a function. (Not significant in compiled scripts) So it works but remember: "(Not significant in compiled scripts)" And this rule is also for ObjEvent.