Context Navigation

Timeline

8:14 PM Ticket #4031 (Calling _DebugArrayDisplay after calling _ArrayDisplay will disable ...) created by anonymous: […] I think the reason is the _ArrayDisplay passes a "0" as the …

4:17 PM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by Jos: Replying to anonymous: > also, the fistr comment (with the link) is clearly spam. maybe it should be deleted? Removed... tnx, it is removed now, ... and please try to calm down a little before typing, as the tone of your post in general normally trigger me to simply ignore these posts. Thanks
12:10 AM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by anonymous: oops, sorry, my bad!! i was blind -- accidentally grouped tickets by type, and missed mine!! Sorry!!!
12:05 AM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by anonymous: also, my ticket (#4025 or #4028?) about a small bug in ObjCreateInterface was deleted? why? >:(

11:47 PM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by anonymous: also, the fistr comment (with the link) is clearly spam. maybe it should be deleted?
11:45 PM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by anonymous: What on earth?! The memory leak is unrelated to what you've done... this does NOT matter: […] […] yes they produce the same number -- that's not the point! i've only choosen the second version because it's clear what it does (we need 2nd pointer, where pointer-size depends on AutoIt's bitness -- 8 if x64 and 4 if x32), while first version is cryptic and dumb and "wrong" -- it tells you nothing about what's going on. the menmory leak WILL and DOES happen every time the error occurs in _GDIPlus_BitmapCreateFromStream. that's why the COM object (the $hStream, which is only a pointer to the stream returned by DllCall; it's not an AutoIt's object, so the Autoit wil not release it automatically on return or even on exit!) so it HAS TO be released manually before returning from the function _GDIPlus_BitmapCreateFromMemory. this: […] should be replaced by this: […] you can leave the 8 * (1 + @AutoItX64) in there if you want. again, this wasn't the issue.

10:01 AM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) closed by J-Paul Mesnage: Works For Me: In fact both are doing the same […]

9:30 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by jchd18: Hi Jpm, I'll have a look at it. But I first need to finish my own timescale UDF and, trust me, it isn't just cake. I write down here preliminary notes. First, GMT has no more any unambiguous meaning since 1972-01-01. The string "GMT" should be replaced by the official name "UTC" everywhere in source and help. Then the purpose of the function here is to produce a datetime string. OK but which datetime? This is untold and the $iType parameter only tells if the input structure is Local or UTC. It seems to me that we need another parameter to decide what the user wants (values for France at the time of writing, UTC+1 and currently +1h summertime): A) the current UTC time string, e.g. "2024-09-28T12:00:00 UTC", with or without the " UTC" suffix or B) his Local timestring, e.g. "2024-09-28T14:00:00+02:00", with or without the "+02:00" offset to UTC or C) yet another datetime format to be decided. Of course, $MS always making things tricky, the structure gives biais the other way, resp. -60 and -60 minutes (biais = UTC - Local). This means we have to subtract that biais from UTC to get local time. This is not done by the function. Also that biais sign should be reversed to be appended to a local time.
8:10 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by J-Paul Mesnage: Hi, Thanks for the ticket but do you have a fix to propose?

2:57 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by jchd18: Description changed
2:25 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by jchd18: Description changed

1:41 PM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by jchd18: Component changed
1:40 PM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) created by jchd18: The function _Date_Time_SystemTimeToDateTimeStr() has two related but …

10:41 AM Ticket #4024 (_DebugSetup - $vReportType = 5 - not works on Windows 11) updated by J-Paul Mesnage: Thanks I encounter such pb but I cannot find a solution Any idea?

6:51 AM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) created by anonymous: to fix: in GDIPlus.au3, in function _GDIPlus_BitmapCreateFromMemory, …

6:00 PM Ticket #4027 (ObjCreateInterface crashes when 3rd param is absent or Default (yet ...) updated by TicketCleanup: Version changed
Automatic ticket cleanup.
5:03 PM Ticket #4027 (ObjCreateInterface crashes when 3rd param is absent or Default (yet ...) created by anonymous: in all versions from 3.3.15.1 up. in earier version incl. 3.3.15.0, it …
4:58 PM Ticket #4026 (COM Object/Map/ScriptingDictionary crash when acessing them in ...) created by anonymous: it's a rather rare teeny-tiny bug, and there's an easy workaround... …

9:00 AM Ticket #4025 (_DebugSetup new $vReportType to combine "1 - Report Log Window" and "4 ...) updated by TicketCleanup: Version changed
Automatic ticket cleanup.
8:30 AM Ticket #4024 (_DebugSetup - $vReportType = 5 - not works on Windows 11) updated by mLipok: Summary changed
8:22 AM Ticket #4025 (_DebugSetup new $vReportType to combine "1 - Report Log Window" and "4 ...) created by mLipok: It is usually good to keep track of the progress, but it would also …
8:18 AM Ticket #4024 (_DebugSetup - $vReportType = 5 - not works on Windows 11) created by mLipok: As the notepad has changed in Windows 11, the option to save the log …

Note: See TracTimeline for information about the timeline view.