Timeline
Mar 31, 2026: Today
- 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: Yesterday
- 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
Note:
See TracTimeline
for information about the timeline view.
