Timeline
Sep 30, 2019:
- 5:00 PM Ticket #3732 (_Excel_BookList) updated by
-
Version changed
Automatic ticket cleanup. - 4:27 PM Ticket #3732 (_Excel_BookList) created by
- _Excel_BookList returns an array of [Object, Name, Path] …
- 10:59 AM Ticket #3731 (Binary() performs hidden and wrong conversion on strings) created by
- One would expect Binary(<string>) to return the binary image of …
Sep 17, 2019:
- 2:28 PM Ticket #3728 (_ArrayTranspose does not create 1D array from 2D array) updated by
- 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
- 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
- […] 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
-
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_CtrlHandlereports the wrong control handle, while@GUI_CtrlIdrefers 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
- 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
- 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
-
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. - 6:46 PM Ticket #3729 (GUICtrlSetDefColor and GUICtrlSetDefBkColor cause inputs to fire other ...) created by
- Hi, was trying to apply some styles to one of my programs and found …
Note:
See TracTimeline
for information about the timeline view.
