Custom Query (3926 matches)
Results (334 - 336 of 3926)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1274 | Rejected | Increase Datatype Ranges | ||
| Description |
I have often attempted to use autoit to compile high range data. A major problem that renders Autoit almost completely worthless in this area is the limitations on math functions. If you were to equate 100000000000000020, autoit would return 1e+300. If you were to equate 100000000000000021, autoit would return 1.#INF. Also, check out this factorial and permutation function written by MSLx Fanboy: http://www.autoitscript.com/forum/index.php?showtopic=13167 Here's a few examples where this script works: _MathPermutation(4, 3) would return the correct answer of 24. _MathPermutation(10, 5) would return the correct answer of 30240. _MathPermutation(20, 5) would return the correct answer of 1860480. but... _MathPermutation(21, 5) would return an incorrect answer of -203093.854699384. I had also attempted to design a script that would calculate the fibonacci sequence of numbers and record them into data files. I noticed that before the results had even a 12 digit length, the returns were suddenly all incorrect, capped to a specific length, and alternating between negative and positive answers. I suggest that AutoIt is made more high range math capable through the addition of an option to change the max limit. By default, every script should run the same as they do now, to avoid overruns in looping miscalculations. But the option should be added to increase this limit. |
|||
| #436 | Fixed | Aut2Exe more efficient from command line? | ||
| Description |
When I used the Aut2Exe GUI to compress a script it came out to 311kb, every time, regardless what I set compression to. When I used the command line with /comp 4 it came out to 309kb, with /comp 3 it came to 310kb, /comp 2 was 311kb. It appears that the GUI is ignoring the compression selection, using the default of /comp 2 (nothing to do with UPX, as turning it off/on works as it should). |
|||
| #3583 | No Bug | AutoIT Window Info (64) produces incorrect position numbers | ||
| Description |
I am currently running AutoIt (64) version 3.3.14.2 on an up-to-date Windows 10 Home laptop (Dell Inspiron 5759). Run AutoIT Window Info (64). Open any application window Move it until AutoIT Window Info shows an X value for Position of 0. The window will actually be 7-8 pixels to the right of 0. Now maximize the application window. Position will be displayed as -7,-7 When a window is maximized, the upper left corner should have Position 0,0 Note that using WinMove and giving the coordinates 0,0 will also incorrectly position the window. |
|||
