Timeline
Oct 17, 2024:
- 11:28 PM Ticket #4024 (_DebugSetup - $vReportType = 5 - not works on Windows 11) closed by
- Fixed: Fixed by revision [13081] in version: 3.3.17.0
- 9:28 AM Ticket #4024 (_DebugSetup - $vReportType = 5 - not works on Windows 11) updated by
- Finally I found a solution Run old notepad if run in Admin mode or display a msgbox containing the Notepad output , the output being store also in the clipboard
Oct 16, 2024:
- 8:08 PM Ticket #4033 (When calling _DateTimeSplit with a string with date only, the returned ...) closed by
- Fixed: Fixed by revision [13080] in version: 3.3.17.0
- 2:32 PM Ticket #2872 (FileDelete set @extended deleted count) updated by
- Replying to vanowm: > @extended seems to get set to non-zero when it failed delete a file ... as you already stated in the forum and assume you're still waiting for an answer? or were you trying to get a speedier answer? Either way: Please do not post in a feature request which is closed 10 years ago!
- 12:37 PM Ticket #2872 (FileDelete set @extended deleted count) updated by
- @extended seems to get set to non-zero when it failed delete a file
- 9:39 AM Ticket #4032 (Unwanted debug output from running scripts in SciTE (from autoit3_x64.exe)) updated by
- Oops, the RC=1 you see is the result of a zero-length .au3 file I guess, you can add some empty lines or comments maybe... But the SetHotKey problem (or HotKeySet) is not relevant to this RC=1, it should be the problem of my environment, because I am running this under Sandboxie, so it can't set the hotkeys... So consider it my problem 😅, you may close this now…
- 8:25 AM Ticket #4032 (Unwanted debug output from running scripts in SciTE (from autoit3_x64.exe)) updated by
- Not sure why you see this. I've tried both x86 & x64 and both end with RC=1 (not 0!) when using no script.
Oct 15, 2024:
- 10:47 PM Ticket #4033 (When calling _DateTimeSplit with a string with date only, the returned ...) created by
- Simple fix, from […] to […] If no one figures this out in these …
- 7:27 PM Ticket #4032 (Unwanted debug output from running scripts in SciTE (from autoit3_x64.exe)) updated by
- The SetHotKey message appears after running autoit3_x64.exe, so it may not be the problem of AutoIt3Wrapper... But after I downloaded the beta version of AutoIt3Wrapper.au3, the message was changed to: !!>Failed Setting Hotkey(s): --> SetHotKey () Restart failed. --> SetHotKey (Ctrl+BREAK) Stop failed. So I think it is because it has problem setting the hotkeys in my case, and by testing, the Stop hotkey (Ctrl-Break) works, but the Restart hotkey (Ctrl-Alt-Break, I guess) is not working, so the message appear... And because you don't see this message, I guess it is only my problem. If it is not a bug, I will try to find a way to remove that message... 💪
- 6:11 PM Ticket #4032 (Unwanted debug output from running scripts in SciTE (from autoit3_x64.exe)) updated by
- I don't get that with the latest Beta version, so please try that first. ​​https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/AutoIt3Wrapper.au3 Jos
- 4:10 PM Ticket #4032 (Unwanted debug output from running scripts in SciTE (from autoit3_x64.exe)) created by
- Open an empty .au3 in SciTE, run it with F5, then see the console …
- 10:37 AM Ticket #4031 (Calling _DebugArrayDisplay after calling _ArrayDisplay will disable ...) closed by
- Fixed: Fixed by revision [13078] in version: 3.3.17.0
- 10:36 AM Ticket #4031 (Calling _DebugArrayDisplay after calling _ArrayDisplay will disable ...) updated by
- Thanks, it is also true after using Userfunc
Oct 13, 2024:
- 8:14 PM Ticket #4031 (Calling _DebugArrayDisplay after calling _ArrayDisplay will disable ...) created by
- […] I think the reason is the _ArrayDisplay passes a "0" as the …
Oct 9, 2024:
- 4:17 PM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by
- 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
- 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
- also, my ticket (#4025 or #4028?) about a small bug in ObjCreateInterface was deleted? why? >:(
Oct 8, 2024:
- 11:47 PM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) updated by
- 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
-
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.
Oct 2, 2024:
- 10:01 AM Ticket #4028 (Potential for a memory leak in _GDIPlus_BitmapCreateFromMemory) closed by
- Works For Me: In fact both are doing the same […]
Sep 28, 2024:
- 9:30 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by
- 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
- Hi, Thanks for the ticket but do you have a fix to propose?
Sep 27, 2024:
- 2:57 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by
-
Description changed
- 2:25 AM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by
-
Description changed
Sep 26, 2024:
- 1:41 PM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) updated by
-
Component changed
- 1:40 PM Ticket #4029 (_Date_Time_SystemTimeToDateTimeStr() wrong output) created by
- The function _Date_Time_SystemTimeToDateTimeStr() has two related but …
Sep 25, 2024:
- 10:41 AM Ticket #4024 (_DebugSetup - $vReportType = 5 - not works on Windows 11) updated by
- Thanks I encounter such pb but I cannot find a solution Any idea?
Note:
See TracTimeline
for information about the timeline view.
