Timeline

Apr 1, 2026: Today

1:08 AM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by mLipok

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.Check5 there 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 mLipok

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 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.Check5 there is the same logic I mean: […]

Mar 31, 2026: Yesterday

9:48 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by 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.

1:25 PM Ticket #4083 (COM Error Handler - not always fires event - when assigning values) updated by Jpm

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 anonymous

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 Jpm

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 anonymous

ps. forgot to remove _WinAPI_IsWow64Process line.

10:52 PM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by Nine

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 Jpm

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 Nine

If the $hWnd does not exist (because the window has not appeared yet …

2:00 AM Ticket #4084 (Windows Message Codes suplementation) updated by TicketCleanup

Version changed
Automatic ticket cleanup.

1:30 AM Ticket #4084 (Windows Message Codes suplementation) updated by mLipok

Component, Type changed

1:30 AM Ticket #4084 (Windows Message Codes suplementation) created by mLipok

please suplement UDF constants […] Usage example: …