Timeline
Apr 26, 2013:
- 10:24 AM Ticket #2337 (Au3Record: Unicode and endianness) updated by
- Confirmed: for instance '=' gets indeed encoded as UTF16-BE in an otherwise UTF16-LE result file.
Apr 24, 2013:
- 2:29 PM Ticket #2337 (Au3Record: Unicode and endianness) created by
- Hi, When recording a script with Au3Record on a French keyboard, the …
Apr 22, 2013:
- 7:51 AM Ticket #2336 (Blockinput (1) not for WACOM Pen with Win8) created by
- All Tablet PC Pen User only under Windows 8 have no function from …
- 12:42 AM Ticket #2333 (AuCheck balks at 5D arrays initializer) updated by
- Pretty lame.
- 12:41 AM Ticket #2334 (Maximum _useful_ array dimension is 24, not 64 as doc says) updated by
- @JP, That's what I said! And yes, it's not exactly a bug, rather an implementation error. @Admiral, This minor issue is both with the language and the documentation. Building to a limit that is non-reachable in practice is at the very least questionnable. That the interpreter allows for a useless series of up to 64 [1] dimensions is pretty stupid: the practical limit (array size) is well below and if we start using [1] dummy dimensions, then why put a limit at all? And the doc should reflect that. BTW, jchd18 = jchd and I've no problem with this ticket closed.
Apr 21, 2013:
- 9:26 AM Ticket #2333 (AuCheck balks at 5D arrays initializer) closed by
- Wont Fix: It is true that AU3check do checking for array dimension <= 4 That is a "known" limitation. I don't thing that with the current implemenation we can go beyond
- 9:18 AM Ticket #2334 (Maximum _useful_ array dimension is 24, not 64 as doc says) closed by
- No Bug: In fact there is no bug as it is not the number of dimension but the global size of the array which is reach 224
- 8:58 AM Ticket #2334 (Maximum _useful_ array dimension is 24, not 64 as doc says) updated by
-
Component changed
64 dimensions is a technical limit, nowhere does it say that it's a useful thing to do. Besides, I'm not sure what you're asking us to do. Lowering the limit? What useful purpose could that possible have? It's also unclear which component you are talking about, AutoIt or the Documentation. I'll assume the later as you have that in your description. - 8:54 AM Ticket #2335 (__WinAPI_EnumWindowsChild() creates results in wrong sequence) closed by
- Fixed: Fixed by revision [7702] in version: 3.3.9.5
Apr 20, 2013:
- 10:21 AM Ticket #2335 (__WinAPI_EnumWindowsChild() creates results in wrong sequence) created by
- In the latest beta version, (and going back to at least the 3.3.7.20 …
Apr 19, 2013:
- 11:05 PM Ticket #2334 (Maximum _useful_ array dimension is 24, not 64 as doc says) created by
- Barring using "dummy" dimensions like [1][1]... the maximum practical …
- 10:56 PM Ticket #2333 (AuCheck balks at 5D arrays initializer) created by
- Au3Check raises an error on array initializer for dimensions > 4. …
- 2:19 PM Ticket #2221 (FileDelete() @error values) updated by
- Replying to Exit: > At least return a @error at all. > Here a function to do the job: > Func _FileDelete($sFile) > $sFile = DllCall('kernel32.dll', 'int', 'DeleteFileW', 'wstr', $sFile) > Return SetError(Not $sFile[0], 0, $sFile[0]) > EndFunc ;==>_FileDelete THat's not what is requested. to have the differention _WinAPIGetLastError() must be called which can be done even after calling the standard FileDelete()
Apr 16, 2013:
- 7:41 AM Ticket #2332 (Uncertainty in the calculations) updated by
- Thanks!
- 7:29 AM Ticket #2332 (Uncertainty in the calculations) closed by
- No Bug: In fact when using Float calculation you cannot expect more than 15 digits precision. That's true under any computer environnment not just AutoIt NO Bug
Apr 15, 2013:
- 7:21 PM Ticket #2332 (Uncertainty in the calculations) created by
- Discrepancy appears for certain values of the variables. example: …
Apr 8, 2013:
- 11:06 AM Ticket #1573 (TCPConnect TCPTimeout) updated by
- This isn't a Forum, please do not post 'bump' or pointless messages in Trac.
- 5:46 AM Ticket #1573 (TCPConnect TCPTimeout) updated by
- Bump?
Apr 7, 2013:
Apr 2, 2013:
- 11:25 PM Ticket #2089 (_IEFormSubmit gives WEnd^ ERROR) updated by
- This issue is fixed in the 3.3.9.x beta stream. The code has not yet been released in a beta, but is posted here: http://www.autoitscript.com/forum/files/file/227-ieau3/ and can be used with the 3.3.9.x beta versions. The code takes advantage of the new autoit version changing COM errors to non-fatal and no longer required in internal COM error handler in IE.au3. There certainly was a logic error in IE.au3 that allowed this to happen, but this code was released and unchanged for years and only recent AutoIt versions/IE versions experience the issue for some reason. Dale
- 9:58 PM Ticket #2331 (Obfuscator bug with the striponly parameter.) closed by
- Fixed: Fixed in v 1.0.30.4
- 4:06 PM Ticket #2331 (Obfuscator bug with the striponly parameter.) created by
- Hi, Seems like I'm unlucky these days with the Obfuscator. Here is …
Mar 29, 2013:
- 10:00 AM Ticket #2328 (Obfuscator includes with parent dir as double dots.) closed by
- Fixed: Fixed in v1.0.30.3.
- 9:18 AM Ticket #2328 (Obfuscator includes with parent dir as double dots.) reopened by
- JPM PMed me an examples that indeed gave me this error so re-opening and will check what the problem is.
Mar 28, 2013:
- 7:38 PM Ticket #2328 (Obfuscator includes with parent dir as double dots.) closed by
- No Bug: Works for me when the files exists. Please discuss on the forums so we can have a dialog.
- 7:31 PM Ticket #2330 (Error occurs when using some object properties with AutoIt) closed by
- No Bug: No bug Use the forum for support requests.
Note:
See TracTimeline
for information about the timeline view.
