Timeline
Dec 12, 2018:
- 4:15 PM Ticket #3683 (Variable must be of type object) closed by
- No Bug: Please use the forum for queries. M23
- 9:24 AM Ticket #1705 (Control Resizing before WinMove) updated by
- Got unexpected behavior using ControlMove() on GUI controls too. Fixed using GUICtrlSetPos(). Maybe this should be stated in documentation.
- 2:32 AM Ticket #3678 (_FileWriteToLine) updated by
- It's very easy to delete a line, just read everything into an array, delete the element of the array containing the line you don't want, write the array back to the file.
Dec 11, 2018:
- 8:27 PM Ticket #3678 (_FileWriteToLine) updated by
- Then do a LineDelete function i don't mind. There aren't any easy way to delete a line atm so…
- 7:17 PM Ticket #3683 (Variable must be of type object) created by
- I use ObjEvent("AutoIt.Error", "function") to handle COM errors so …
Dec 6, 2018:
- 8:26 PM Ticket #3682 (GuiCtrlCreatePic and the "set width and height to 0" feature) created by
- The help file says : To set the picture control to the same size as …
- 12:00 AM Ticket #3681 (In the section "Variables" the prefix "o" is not described.) updated by
-
Version changed
Automatic ticket cleanup.
Dec 5, 2018:
- 11:47 PM Ticket #3681 (In the section "Variables" the prefix "o" is not described.) created by
- In the "Language Reference - Variables" section, the "Names of …
- 8:11 PM Ticket #3680 (Improve _ArrayBinarySearch function) updated by
- You want it - you write it. Or at least a first attempt so we can see exactly what it is you wish to see implemented. M23
- 8:30 AM Ticket #3238 (Au3info doesn't compensate for DPI scaling) updated by
- Adding DllCall("User32.dll","bool","SetProcessDPIAware") makes the scripts aware of the DPI scaling but the AutoIt v3 Window Info does not take DPI scaling into account. To find the correct mouse position, one would need to take the position values given by the Window Info and then multiply it manually by whatever you have your scaling set to. If you have it set to 150%, then you multiply by 1.5. Is this something that will eventually be addressed with the Window Info? Perhaps having the Window Info detect what scaling is set to or allow users to manually enter in what scaling they are using so that the mouse positions will be accurate?
Dec 3, 2018:
- 4:00 PM Ticket #3680 (Improve _ArrayBinarySearch function) updated by
-
Version changed
Automatic ticket cleanup. - 3:10 PM Ticket #3680 (Improve _ArrayBinarySearch function) created by
- Think about the binary search not found case, return -1, then we …
- 1:35 PM Ticket #3238 (Au3info doesn't compensate for DPI scaling) updated by
- <snip>
Nov 25, 2018:
- 3:41 PM Ticket #3678 (_FileWriteToLine) updated by
- > this 3 modes idea seems great imo > it should please everybody I disagree, a function with the word Write in it shouldn't be deleting lines. If you think writing means deleting then I can't help with that.
Nov 24, 2018:
- 9:00 PM Ticket #3679 (InetGet / InetRead - Disable Cache Option) updated by
-
Version changed
Automatic ticket cleanup. - 8:11 PM Ticket #3679 (InetGet / InetRead - Disable Cache Option) created by
- I would like to have a option to disable the automatic cache of these …
Nov 22, 2018:
- 8:28 PM Ticket #3678 (_FileWriteToLine) updated by
- this 3 modes idea seems great imo it should please everybody
- 10:37 AM Ticket #3678 (_FileWriteToLine) updated by
- Not too difficult - but it means using 3 modes instead of the existing 2: […] Comments? M23
- 10:18 AM Ticket #3678 (_FileWriteToLine) updated by
- I see the problem - and I remember why it happens. There was considerable discussion when the function was rewritten some years ago as to whether this "delete a line" functionality should be retained as it removes the possibility of replacing an existing line with a blank one. If it were retained, the only option to "overwrite" with a blank line was to remove the line completely and then rewrite a new blank one, which required 2 calls to the function. The consensus as I recall was that overwriting a line with a blank was more likely than deleting a line - and so the code was amended, but not the Help file. So the question resurfaces - which of the 2 functionalities is more useful? Or should both be available? I will take a look and see what might be done to do this without overcomplicating either the syntax or the code. M23
- 7:21 AM Ticket #3678 (_FileWriteToLine) updated by
- ok, with a file with those lines : 1 2 3 4 doing this _FileWriteToLine($file, 3, "", 1) was result in 1 2 4 but now the result is 1 2 4
Nov 21, 2018:
- 10:27 PM Ticket #3678 (_FileWriteToLine) updated by
- Could you try to explain what you mean exactly, as that sentence is not clear to me? Jos
- 7:27 PM Ticket #3678 (_FileWriteToLine) created by
- _FileWriteToLine($file, $line, "", 1) this was removing a line now it …
- 9:50 AM Ticket #3575 (TCP functions slow and TCPCloseSocket with shutdown) updated by
- Replying to Jpm: > Sorry to ask so late, can i have repro scripts so I can analyse and try to find a solution > THanks JP, It looks like we need to do a shudown() before the closesocket() in F_TCPCloseSocket() to stop traffic from being accepted. Read this post and the next 4 posts: https://www.autoitscript.com/forum/topic/196642-tcpsend-bug/?do=findComment&comment=1410377 Jos
Nov 16, 2018:
- 3:13 PM Ticket #3677 (_FileListToArrayRec()'s 2nd parameter ($sMask) seems case sensitive.) updated by
- Client system had _ArrayDisplay() show different results depending on $sMask's case (searching a FAT32 USB flash drive using AutoIt v3.3.14.2 on Windows XP Professional x32 SP3). Will see if I can provide scenario reproducing script.
Nov 14, 2018:
- 4:40 PM Ticket #3675 ($tagNETRESOURCE: Add constants) updated by
- The 2 that have the same value should perhaps be ignored for another reason: MSDN says that they are for XP and earlier.
- 9:17 AM Ticket #3677 (_FileListToArrayRec()'s 2nd parameter ($sMask) seems case sensitive.) closed by
- No Bug: This UDF is using FileFindFirstFile() which is indicated to be not case sensitive. Closing as no bug for the moment until a replication script and scenario is provide that proves otherwise. Jos
- 12:19 AM Ticket #3677 (_FileListToArrayRec()'s 2nd parameter ($sMask) seems case sensitive.) updated by
- I just ran the example script in the help file, after changing some of the extensions of files to upper case, and it still picked up the upper case files, as well as the lower case ones. I also changed the search parameter to *.EXE on one of the searches, and it still found both upper and lower case file names. Your bug report is wrong as far as I can see.
Nov 13, 2018:
- 4:47 PM Ticket #3677 (_FileListToArrayRec()'s 2nd parameter ($sMask) seems case sensitive.) created by
- Setting _FileListToArrayRec()'s 2nd parameter ($sMask) to "*.jpeg" …
- 6:00 AM Ticket #3676 ($tagResource Help lacks some DisplayTypes) updated by
-
Version changed
Automatic ticket cleanup. - 5:02 AM Ticket #3676 ($tagResource Help lacks some DisplayTypes) updated by
- c.haslam
- 5:01 AM Ticket #3676 ($tagResource Help lacks some DisplayTypes) updated by
- $tagNETRESOURCE only has 4 of the possible options. I suggest that the others be copied from https://msdn.microsoft.com/en-us/library/windows/desktop/aa385353(v=vs.85).aspx
- 5:00 AM Ticket #3675 ($tagNETRESOURCE: Add constants) updated by
-
Version changed
Automatic ticket cleanup. - 4:59 AM Ticket #3676 ($tagResource Help lacks some DisplayTypes) created by
- 4:53 AM Ticket #3675 ($tagNETRESOURCE: Add constants) updated by
- c.haslam
- 4:52 AM Ticket #3675 ($tagNETRESOURCE: Add constants) updated by
- The following constants appear to be missing from WinNet.au3: ; DisplayType Global Const $RESOURCEDISPLAYTYPE_GENERIC = 0x00000000 Global Const $$RESOURCEDISPLAYTYPE_DOMAIN = 0x00000001 Global Const $RESOURCEDISPLAYTYPE_SERVER = 0x00000002 Global Const $RESOURCEDISPLAYTYPE_SHARE = 0x00000003 Global Const $RESOURCEDISPLAYTYPE_FILE = 0x00000004 Global Const $RESOURCEDISPLAYTYPE_GROUP = 0x00000005 Global Const $RESOURCEDISPLAYTYPE_NETWORK = 0x00000006 Global Const $RESOURCEDISPLAYTYPE_ROOT = 0x00000007 Global Const $RESOURCEDISPLAYTYPE_SHAREADMIN = 0x00000008 Global Const $RESOURCEDISPLAYTYPE_DIRECTORY = 0x00000009 I copied them from https://msdn.microsoft.com/en-us/library/windows/desktop/aa385353(v=vs.85).aspx There are two more there, but they have the same value (which I find surprising): Global Const $RESOURCEDISPLAYTYPE_TREE = 0x0000000A Global Const $RESOURCEDISPLAYTYPE_NDSCONTAINER = 0x0000000A Perhaps these two should not be added for this reason.
- 4:41 AM Ticket #3675 ($tagNETRESOURCE: Add constants) created by
Note:
See TracTimeline
for information about the timeline view.
