Timeline
Nov 13, 2024:
- 9:51 AM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- I would like to add that I much prefer portable apps and also am in great favour of them being fully stealth, ie, leaving no trace on the system they are run. No trace means no empty files or folders left behind. I often switch to new apps that have this as standard if my current one isn't fully stealth. Although I understand that installing apps for multiple users requires using the User folders, etc, I think that these days all apps should be fully portable and fully self contained. App files are small enough that very little extra disk space is required to add them to several set ups. For example, my AutoIT/SCiTe portable set up is 76MB. That includes 4 X-Launchers to fully portablise the app that claims to be portable but leaves things on my PC. I mean no disrespect, after all, this is a free app and I am only learning the basics. I just wish to point out that there is a whole community of supporters for portable, and stealth, apps.
Nov 11, 2024:
- 11:59 PM Ticket #4035 (Prevent 32-bit scripts from having way more false positives than 64-bit) updated by
- Replying to Jos: > Replying to lwc: > > Where in the forum was it discussed the differences between 32-bit and 64-bit where it comes to false positives? > > Don't know, but that shouldn't be a real surprise. Why not?
- 11:59 PM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) updated by
- Replying to Jos: > Just had a more detailed look and the default for #AutoIt3Wrapper_UseX64 is really "N". > So when you just provide the directive without any other option: > > {{{ > #AutoIt3Wrapper_UseX64 > }}} > > It will default to "N". The Menu (Ctrl+F7) will default to the version installed. What about Build, does it ignore #AutoIt3Wrapper_UseX64?
- 10:35 AM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) updated by
-
Summary changed
- 8:47 AM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) closed by
- Fixed
- 8:47 AM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) updated by
- Replying to lwc: > Either way the documentation is not correct. It should be fixed to state the default is based on the AUT2EXE version. > > Plus it should stave #AutoIt3Wrapper_Compile_both=y bypasses/ignores it. Just had a more detailed look and the default for #AutoIt3Wrapper_UseX64 is really "N". So when you just provide the directive without any other option: […] It will default to "N". The Menu (Ctrl+F7) will default to the version installed.
- 8:45 AM Ticket #4035 (Prevent 32-bit scripts from having way more false positives than 64-bit) updated by
- Replying to lwc: > Where in the forum was it discussed the differences between 32-bit and 64-bit where it comes to false positives? Don't know, but that shouldn't be a real surprise.
Nov 10, 2024:
- 4:01 PM Ticket #4035 (Prevent 32-bit scripts from having way more false positives than 64-bit) updated by
- Where in the forum was it discussed the differences between 32-bit and 64-bit where it comes to false positives?
- 3:58 PM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) updated by
- Either way the documentation is not correct. It should be fixed to state the default is based on the AUT2EXE version. Plus it should stave #AutoIt3Wrapper_Compile_both=y bypasses/ignores it.
- 1:17 PM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) updated by
- How did you determine that it defaults to yes? It does default to N, but when you have installed the x64 AutoIt3 version, then obviously when no directive is provided, the default will be the x64 AUT2EXE version. So, the default is depending on the installed default AutoIt3 version (x86/x64) Agree? (so maybe this did belong in the forum! ;) )
- 1:09 PM Ticket #4035 (Prevent 32-bit scripts from having way more false positives than 64-bit) closed by
- No Bug: This has been beaten to dead many times in the forum, so I honestly have no idea why you opened an BUG report being around since 2010!
- 12:34 PM Ticket #4035 (Prevent 32-bit scripts from having way more false positives than 64-bit) created by
- When using #AutoIt3Wrapper_Compile_both=y the resulting compiled …
- 12:30 PM Ticket #4034 (Fix the documentation about #AutoIt3Wrapper_UseX64) created by
- [https://www.autoitscript.com/wiki/AutoIt3Wrapper_Directives …
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
Note:
See TracTimeline
for information about the timeline view.
