Timeline
Apr 21, 2026: Yesterday
- 3:38 PM Ticket #4089 (Fixing __ArrayDisplay_SortArrayStruct dll declaration) updated by
- For info, the following pattern is a bit more precise, taking care of eventual several spaces or Tabs in the line, between the word Static and the word Local. Gladly we don't find this case in any of our include files (or the lines would have appeared in the results of my preceding post) […]
Apr 20, 2026:
- 9:40 PM Ticket #4089 (Fixing __ArrayDisplay_SortArrayStruct dll declaration) updated by
-
Component changed
- 7:59 PM Ticket #4089 (Fixing __ArrayDisplay_SortArrayStruct dll declaration) updated by
- Jean-Paul, for the record, I ran the following RegEx pattern in a loop on all include files (155) The negative lookahead part didn't catch 7 "Static Local" lines found in WinAPIRes.au3 and WinAPISys.au3, which seems correct as they are valid lines. […]
- 5:26 PM Ticket #4089 (Fixing __ArrayDisplay_SortArrayStruct dll declaration) closed by
- Fixed: Fixed by revision [13371] in version: 3.3.19.0 Fixed #4089: Static not declared as Local in some UDF.
- 1:57 PM Ticket #4089 (Fixing __ArrayDisplay_SortArrayStruct dll declaration) updated by
- (Forgot my username)
- 1:56 PM Ticket #4089 (Fixing __ArrayDisplay_SortArrayStruct dll declaration) created by
- How to reproduct : Global Const $hDll = 0 #include <Array.au3> What …
Apr 16, 2026:
- 10:04 AM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Owner, Status changed
Fix sent to Jon
Apr 15, 2026:
- 3:21 PM Ticket #4086 (Bug with IniReadSectionNames if file is coded with UTF-8-BOM) closed by
- Fixed: Fixed by revision [13369] Added #4086: Some precision about UTF8 with BOM ini file for ini functions.
Apr 14, 2026:
- 4:41 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) closed by
- No Bug: Hi so I close the ticket
Apr 8, 2026:
- 9:12 AM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- Without any comments I will close the ticket
Apr 7, 2026:
- 8:54 AM Ticket #4088 (SciTE opens for a few seconds, then closes.) closed by
- Works For Me: Pls use the forum for questions. Jos
- 1:13 AM Ticket #4088 (SciTE opens for a few seconds, then closes.) created by
- Just started using AutoIt and SciTE again since upgrading to Windows …
Apr 4, 2026:
- 10:48 AM Ticket #4086 (Bug with IniReadSectionNames if file is coded with UTF-8-BOM) updated by
- It is a bug in MS API used by AutoIt It is true also for IniReadSection and IniRead Those API was cerlainly created before UTF8 with BOM support The only think I can do is to make a warning in the doc Cheers […]
Apr 3, 2026:
- 8:29 PM Ticket #4087 (Colorize "Volatile" Function declarations also.) updated by
- for reference discussion was taken here: https://www.autoitscript.com/forum/topic/205465-uploaded-a-new-version-of-the-scite4autoit3exe-v2131616391/page/15/#findComment-1551267 Was it fixed ? should this ticket status been changed from rejected to other state ?
- 8:25 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Replying to mLipok:
> but still valid question are:
>
> why this following is quite fine handled:
> {{{#!autoit
> $oMAP_Object.FakeMapElement.Check6 ; NO ERROR
> }}}
>
> and this following fires
Variable must be of type "Object"> {{{#!autoit > $oMAP_Object.FakeMapElement.Check6 = 1 ; ERROR OCCURS > }}} so as this is not related toCOM Error Handlershould I open separate Ticket ? Hm.... as this is experimental feature ... what is your aproach to this two mentioned/quoted cases. - 3:16 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- As I said check6 has nothing to do with Object so no firing condition can occur for Check4 just firing no message I will change the status with fix sent to Jon as soon I like my proposal Cheers
Apr 2, 2026:
- 11:10 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- Replying to Jpm: > I solve check4 What type of error message is put into console ? Is it solve also check6 ?
- 11:03 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Replying to Jpm:
> I think Check6 cannot fire a com handler as the datatype is Map
Yes I agree.
> I agree the error message refer to Object instead of Map(?)
I agree that.
Is it good or wrong message ?
Should we catch them ? and protect execution like in case of object ? or not ?
[…]
but still valid question are:
why this following is quite fine handled:
[…]
and this following fires
Variable must be of type "Object"[…] - 8:57 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- I think Check6 cannot fire a com handler as the datatype is Map I agree the error message refer to Object instead of Map(?) Not sure I can differentiate it as Dot notation is valid for both I solve check4
- 8:13 PM Ticket #4087 (Colorize "Volatile" Function declarations also.) closed by
- Rejected: mmm.. that's an dynamic issue as the old stuff works fine. I am closing it here and bring it back to the forum. PM will follow soon. Jos
- 6:37 PM Ticket #4087 (Colorize "Volatile" Function declarations also.) created by
-
Because
Volatileis experimental, I'm not sure if this is a bug, or … - 11:47 AM Ticket #4084 (Windows Message Codes suplementation) closed by
- Fixed: Fixed by revision [13355] Added #4084: $WM_DPI* message code constants.
- 10:23 AM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- Who is anonymous?
Apr 1, 2026:
- 11:09 PM Ticket #4086 (Bug with IniReadSectionNames if file is coded with UTF-8-BOM) updated by
- @JPM please also read: https://www.autoitscript.com/forum/topic/206029-ini-functions-and-ini-file-encoding/#findComment-1483659 and: https://www.autoitscript.com/forum/topic/206029-ini-functions-and-ini-file-encoding/#findComment-1483660 also: https://www.autoitscript.com/forum/topic/174335-file-encoding-problem/
- 10:33 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- Replying to Jpm: > Thanks to confirm > In fact Check2 and Check4 return a @error = 1 > I don't know if it is intended not firing > Cheers hm... I'm little confused Did you mean > In fact Check2 and Check5 return a @error = 1 > I don't know if it is intended not firing ?
- 10:23 PM Ticket #4086 (Bug with IniReadSectionNames if file is coded with UTF-8-BOM) updated by
-
Description changed
- 9:08 PM Ticket #4086 (Bug with IniReadSectionNames if file is coded with UTF-8-BOM) updated by
- see discussion at https://www.autoitscript.com/forum/topic/213616-bug-with-inireadsectionnames-if-file-is-coded-with-utf-8-bom/#comment-1551213
- 9:08 PM Ticket #4086 (Bug with IniReadSectionNames if file is coded with UTF-8-BOM) created by
- I have an ini-file that is formatted with UTF-8-BOM. If the file does …
- 8:44 AM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- Thanks to confirm In fact Check2 and Check4 return a @error = 1 I don't know if it is intended not firing Cheers
- 1:08 AM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Replying to mLipok:
> Replying to Jpm:
> > I find out with the above script that $oMAP_object.FakeObject3.Check5 is not firing either
> > Can you confirm?
>
> yes.
>
> but take a look on previous one:
>
; ... but maybe it is intentional to not FIRE _ComErrorHandler() as $oMAP_object.FakeObject1 is treated as MAP ELEMENT thus Check2 is also treated as MAP element and thus can be created on the fly> > maybe here in case of$oMAP_object.FakeObject3.Check5there is the same logic > I mean: > {{{#!autoit > ; _ComErrorHandler() IS NOT FIRED but AutoIt PROPERLY continue processing next line - due COM ERROR HANDLER was used and FIXED in #3167 > ; ... but maybe it is intentional to not FIRE _ComErrorHandler() as $oMAP_object.FakeObject3 is treated as MAP ELEMENT thus Check5 is also treated as MAP element and thus can be created on the fly > MsgBox(0, @ScriptLineNumber & " : $oMAP_object.FakeObject3.Check5", $oMAP_object.FakeObject3.Check5) > }}} Modified repro script: […] #REMARK => .Check2 And .Check5 needs To be explained #REMARK => both .Check4 and .Check6 should fires _ComErrorHandler() and show the console message also AutoIt should not ends With: Variable must be of type "Object" - 1:00 AM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- Replying to donnyh13: > For what it's worth, I can confirm that $oMAP_object.FakeObject3.Check5 does not fire for me, the same as it doesn't fire with $oMAP_object.FakeObject1.Check2. Thanks.
- 12:58 AM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Replying to Jpm:
> I find out with the above script that $oMAP_object.FakeObject3.Check5 is not firing either
> Can you confirm?
yes.
but take a look on previous one:
; ... but maybe it is intentional to not FIRE _ComErrorHandler() as $oMAP_object.FakeObject1 is treated as MAP ELEMENT thus Check2 is also treated as MAP element and thus can be created on the flymaybe here in case of$oMAP_object.FakeObject3.Check5there is the same logic I mean: […]
Mar 31, 2026:
- 9:48 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- For what it's worth, I can confirm that $oMAP_object.FakeObject3.Check5 does not fire for me, the same as it doesn't fire with $oMAP_object.FakeObject1.Check2.
- 1:25 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- I find out with the above script that $oMAP_object.FakeObject3.Check5 is not firing either Can you confirm?
- 1:08 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- No error ? Did not catch that the handle in invalid ? Did not inform the user of the reason of failure ?
- 8:23 AM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- I don't know what you want to prouve but your script miss a WinWaitActive("AutoIt v3 Window Info", "") Cheers
Mar 30, 2026:
- 11:02 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- ps. forgot to remove _WinAPI_IsWow64Process line.
- 10:52 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- You are right. I shouldn't use that internal function. On the other hand, what is the use of that line ? None ! So instead of returning a valid id, it is returning a false PID. I truly believe that any (internal / external) functions should be self-secure. But that may be just me. Anyway, just run that script and you will see what I mean : […]
- 5:41 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by
- This is an internal function perhaps not the best naming If you prouve That the other internal function _GUICtrl_TagOutProcess() is not doing the job I will do something Cheers
- 4:18 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) created by
- If the $hWnd does not exist (because the window has not appeared yet …
- 2:00 AM Ticket #4084 (Windows Message Codes suplementation) updated by
-
Version changed
Automatic ticket cleanup. - 1:30 AM Ticket #4084 (Windows Message Codes suplementation) updated by
-
Component, Type changed
- 1:30 AM Ticket #4084 (Windows Message Codes suplementation) created by
- please suplement UDF constants […] Usage example: …
Mar 28, 2026:
- 7:59 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- most complex example: https://www.autoitscript.com/forum/topic/213563-catching-com-errors-when-assigning-a-value-to-chained-object/page/2/#findComment-1551168 […] #REMARK => .Check2 needs To be explained #REMARK => both .Check4 and .Check6 should fires _ComErrorHandler() and show the console message also AutoIt should not ends With: Variable must be of type "Object"
- 7:02 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
- […] […] ..that is a simpler example (from a forum post)https://www.autoitscript.com/forum/topic/213563-catching-com-errors-when-assigning-a-value-to-chained-object/page/2/#findComment-1551164 For now we can wrap it in Execute() to avoid the crash while it gets fixed.
- 4:50 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Description changed
- 4:48 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Description changed
- 4:41 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Description changed
- 4:37 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Description changed
- 4:34 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by
-
Description changed
- 4:33 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) created by
- This issue is continuation for: …
- 3:35 PM Ticket #3167 (COM Error Handler - not always fires event) updated by
-
Description changed
Mar 28, 2026:
- 8:58 AM Ticket #4080 (Tree View Extended Styles) closed by
- Fixed: Fixed by revision [13338] Added #4080: _GUICtrlTreeView_SetExtendedStyle(), GUICtrlTreeView_GetExtendedStyle(), _GUICtrlTreeView_SetExtendedChecked() and _GUICtrlTreeView_GetExtendedChecked()
- 7:41 AM Ticket #4082 (_GUICtrlTab_GetItemText() Crash in X64) closed by
- Fixed: Fixed by revision [13336] in version: 3.3.19.0 Fixed #4082: _GUICtrlTab_GetItemText() Crash in X64
- 7:15 AM Ticket #4082 (_GUICtrlTab_GetItemText() Crash in X64) updated by
-
Summary changed
Mar 27, 2026:
- 1:40 AM Ticket #4082 (_GUICtrlTab_GetItemText() Crash in X64) updated by
- Replying to Jpm: > Can i have a repro script? > I remember I have a very long time to debug this stuff > Thanks Check discussion above
Mar 26, 2026:
- 11:32 PM Ticket #4082 (_GUICtrlTab_GetItemText() Crash in X64) updated by
- Can i have a repro script? I remember I have a very long time to debug this stuff Thanks
- 11:57 AM Ticket #4082 (_GUICtrlTab_GetItemText() Crash in X64) created by
- In GuiCtrlInternals.au3 replace line : […] with […] See …
Note:
See TracTimeline
for information about the timeline view.
