Timeline



Apr 8, 2026:

9:12 AM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by Jpm
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 Jos
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 ranier25@…
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 Jpm
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 mLipok
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 mLipok
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 to COM Error Handler should 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 Jpm
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 mLipok
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 mLipok
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 Jpm
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 Jos
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 donnyh13
Because Volatile is experimental, I'm not sure if this is a bug, or …
11:47 AM Ticket #4084 (Windows Message Codes suplementation) closed by Jpm
Fixed: Fixed by revision [13355] Added #4084: $WM_DPI* message code constants.
10:23 AM Ticket #4085 (__GUICtrl_IsWow64Process($hWnd) issue) updated by Jpm
Who is anonymous?
Note: See TracTimeline for information about the timeline view.