Timeline



Sep 17, 2019:

2:28 PM Ticket #3728 (_ArrayTranspose does not create 1D array from 2D array) updated by jchd18
Another option is to leave any 1D input untouched and return the same 1D array (without error). People needing to differentiate between $A[1][5] (i.e. a row of Excell with values in the first 5 columns) and $A[5][1] (i.e. a column of Excell with values in the first 5 rows) will have to explicitely provide 2D arrays in one of the forms above. All in all I believe this is what we should do about the question, but others may have a diverging opinion.
2:39 AM Ticket #3728 (_ArrayTranspose does not create 1D array from 2D array) updated by Nine
I would then suggest to add a second optional parameter to force 2D into 1D. By default false, so no script breaking. True would provide a !D array under all circumstances.

Sep 15, 2019:

5:43 PM Ticket #3730 (Send("{BROWSER_HOME}") does not work anymore with newest Win10 and ...) created by Exit
[…] does not work in Windows 10 Version 1903 and Autoit Version …

Sep 2, 2019:

2:19 PM Ticket #3729 (GUICtrlSetDefColor and GUICtrlSetDefBkColor cause inputs to fire other ...) updated by Enrico Boldori <mainmaster@…>
In that case I'll leave here a possibile workaround for future reference. […] We must use GUICtrlGetHandle(@GUI_CtrlId) to get the handle because @GUI_CtrlHandle reports the wrong control handle, while @GUI_CtrlId refers to the correct control that generated the event. Thanks for the quick reply
11:31 AM Ticket #3729 (GUICtrlSetDefColor and GUICtrlSetDefBkColor cause inputs to fire other ...) closed by Melba23
Wont Fix: I think the explanation given in that Trac response is quite clear - fixing the bug would require a complete rewrite of the GUI generation code of AutoIt and that is something which the Devs are not prepared to undertake. So as suggested in the multitude of threads which have reported the same thing, do not colour buttons! We usually suggest using a slightly larger underlying disabled label and changing its colour as and when required. M23
10:36 AM Ticket #3729 (GUICtrlSetDefColor and GUICtrlSetDefBkColor cause inputs to fire other ...) updated by Enrico Boldori <mainmaster@…>
Second update: found an old closed issue (#376) for the same problem that was marked as Won't Fix without any real explanation or solution provided.

Sep 1, 2019:

10:32 PM Ticket #3729 (GUICtrlSetDefColor and GUICtrlSetDefBkColor cause inputs to fire other ...) updated by Enrico Boldori <mainmaster@…>
Update: the issue is actually related to the background color of a button. I have attached a second example, please try the following: * Run the example, immediately click inside the input, change the text and press ENTER. A single event is fired * Cycle through the controls with the TAB button until the focus is again in the input field. Change the text and press ENTER again. Two events will be fired. * Try moving the call to GUICtrlSetBkColor() under the first button and notice the same behaviour.
10:28 PM AutoIt - Buttons background color issue.au3 attached to Ticket #3729 by Enrico Boldori <mainmaster@…>
Second reproduction script
6:47 PM AutoIt - GuiCtrlSetDefXXColor double event bug.au3 attached to Ticket #3729 by Enrico Boldori <mainmaster@…>
Reproduction script for the reported issue
6:46 PM Ticket #3729 (GUICtrlSetDefColor and GUICtrlSetDefBkColor cause inputs to fire other ...) created by mainmaster@…
Hi, was trying to apply some styles to one of my programs and found …

Aug 31, 2019:

12:41 AM Ticket #3728 (_ArrayTranspose does not create 1D array from 2D array) updated by jchd18
The problem with (mathematical) vectors is that not all languages differentiate between row- and column-vectors. I mean AutoIt has to use 2D to represent a column vector. Given some 1D data [1, 2, 3] as input, its transpose is forcibly 2D, namely [[1], [2], [3]] and this clearly changes the dimension order. Transposing again that output isn't stable, since the function currently exchanges dimension 1 & 2, returning [[1, 2, 3]]. It could be considered sensible to ignore dimensions whose value is 1, but this gives way to another complaint: if my original input is 2D like [[1], [2], [3]], then transposing it twice isn't stable and doesn't respect the original dimension order, giving [1, 2, 3] which is 1D only. So, either way the implementation of Transpose choose, it will make half of AutoIt users angry. I don't know how to solve that dilemna. Agreed, the second example of this help topic is misleading in this respect. Note that outside pure mathematical application or language (Mapple, Mathematica, Octave, MatLab, R, ...) it's quite rare to have to take utter care of vector organisation (row or column). Adding an explicit note about this in the help would only confuse 99% of users, I'm afraid.

Aug 30, 2019:

6:58 PM Ticket #3728 (_ArrayTranspose does not create 1D array from 2D array) updated by Jos
Please read the guidelines for bug reports again and be complete in your report! --quote-- Bug Report Guidelines You must provide a short test script that reproduces the problem. The script should be no more than the bare minimum code necessary to reproduce the problem. Test the reproduction script with both the ​latest stable and ​latest beta versions of AutoIt. Check the links to ensure you have the latest versions, AutoIt is updated frequently. Please choose the correct version and component for the ticket. -- unquote Thanks Jos
6:43 PM Ticket #3728 (_ArrayTranspose does not create 1D array from 2D array) created by Nine
In the example of _ArrayTranspose, it states that a 2D array with …
Note: See TracTimeline for information about the timeline view.