Timeline
Apr 30, 2024:
- 6:47 PM Ticket #4005 (Empty ReDim make Autoit crash) updated by
- I understand and it should be treated more elegant as a runtime error. My point was if you write invalid code then it's a high chance to get bad or unexpected behavior. By the way, are you allowed to compile from SciTe if you have syntax errors?
- 6:17 PM Ticket #4005 (Empty ReDim make Autoit crash) updated by
- Replying to Andreik: > Both ReDim throw a syntax error in SciTe. What do you expect more? AutoIt3 shouldn't hard crash.
- 11:51 AM Ticket #4005 (Empty ReDim make Autoit crash) updated by
- Both ReDim throw a syntax error in SciTe. What do you expect more?
Apr 27, 2024:
- 4:55 PM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- Read my answer in whatever way you feel like, but you know very well you are asking for something that is a LWC special and is not making any sense doing it that way, like you more or less state yourself ... hence "nonsense"
- 3:48 PM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- There's really no reason for offending like this.
Apr 26, 2024:
- 3:30 AM Ticket #4007 (Inconsistent pointer arithmetic) updated by
- Some other variant type have the same strange behavior like the Default keyword : Default + (Int32)2 = (Double)1 Default - (Int32)2 = (Int32)-2 Default * (Int32)2 = Default Default / (Int32)2 = Default
Apr 25, 2024:
- 11:00 PM Ticket #4007 (Inconsistent pointer arithmetic) created by
- Pointers have several inconsistencies during mathematical operations, …
- 11:41 AM Ticket #4005 (Empty ReDim make Autoit crash) updated by
-
Issue confirmed.
IMHO: AutoIt should throw AutoIt error something like:
Array ReDim has not set number of subscripts.
Apr 24, 2024:
- 8:43 PM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- Excuse me, but this last post is really nonsense, so I am done debating this. Request stays closed as "No Bug"
- 7:39 PM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- Which is why I think it should be part of SciTE. While technically it's not related, it is the place that is most likely to be used for compilations, and this way once you exit it then it will delete leftovers from all edited scripts.
- 6:45 PM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- SciTE parameter? SciTE doesn't play any role in this! Do you mean AutoIt3Wrapper parameter? So you expect AutoIt3Wrapper the delete it? This is not going to happen since, when somebody runs AutoIt3Wrappper for some reason mistakenly uses the parameter -portable, that person will potentially lose the total content of %localappdata%/autoit v3/* with all its config settings for SciTE and Utilities and I will not want to be held responsible for that. When you need to make this change in your environment then feel free to do so in your version or write your own wrapper to do the extra steps as that can be too hard for your specific requirements.
- 9:02 AM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
-
Would you consider at least to accept a command line parameter like
-portableto SciTE.exe, which will delete the folder upon exiting SciTE?
Apr 19, 2024:
- 11:33 AM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
- Let's agree to disagree: I will use the same directory in AutoIt3Wrapper as aut2exe does. You are welcome to make whatever change locally you feel is desired for yourself.
- 10:30 AM Ticket #3987 (Aut2Exe creates a temp folder without deleting it) updated by
-
Because 1 bug doesn't mean there should be 2.
The alternatives are:
1. Just make SciTE in general delete
%LocalAppData%\AutoIt v3\on exit 1. Allow both AutoIt3Wrappper and autoit.exe to use %temp\AutoIt v3\ instead
Apr 16, 2024:
- 2:21 PM Ticket #4006 (incomplete read missing key in IniReadSection) updated by
- yes i understand. Thank you very much. and I have a suggestion to add a size limit note every time the developer uses this function. to avoid duplicate bug reports
- 8:26 AM Ticket #4006 (incomplete read missing key in IniReadSection) closed by
- No Bug: The IniRead() function isn't broken and uses the standard GetPrivateProfileString() from the kerner32.dll which has a limitation for: […] https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-getprivateprofilesection#parameters
- 1:42 AM Ticket #4006 (incomplete read missing key in IniReadSection) updated by
- This function is also broken in the latest version 3.3.16.1
- 1:32 AM Ticket #4006 (incomplete read missing key in IniReadSection) created by
- incomplete read missing key in IniReadSection when the value length is …
Note:
See TracTimeline
for information about the timeline view.
