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: […]