Timeline
Jun 22, 2017:
- 9:34 PM Ticket #3557 (Can't concatenate other strings to BinaryToString) closed by
- No Bug: You are misusing the parameter to BinaryToString. […] Please, next time, post in the Help forum before creating a ticket.
Jun 21, 2017:
- 9:09 PM Ticket #3557 (Can't concatenate other strings to BinaryToString) created by
- […] Any kind of string concatenation after BinaryToString() is …
- 3:47 PM Ticket #3549 (GUI Reference - OnEvent Mode: missing include in code sample) updated by
- Thanks just post what what you optional suggestion can be
- 3:34 PM Ticket #3555 (_GUICtrlRichEdit_StreamToVar with > 2048 characters) updated by
- I don't undertstand how updating an in parameter can solve any issue. If I run the Help example and I paste more the 2048 char it works fine. So can I have a repro script? Thanks
Jun 19, 2017:
- 4:37 PM Ticket #3554 (Ini functions should be documentated as containing limitations) closed by
- Rejected
Jun 13, 2017:
- 4:35 PM Ticket #3556 (Run, RunWait and similar calls fail with large amounts of data) closed by
- No Bug: You have a thread running about this problem. Wait until you actually find out that there is a bug before opening a ticket - at present I would bet on a problem with your code rather than with AutoIt itself. M23
- 3:15 AM Ticket #3556 (Run, RunWait and similar calls fail with large amounts of data) updated by
- The "bug" isn't clear at all, and your post in GH&S is even less clear. Please post the full script you're having problems with and not just tiny bits and pieces of it if you want to demonstrate a bug.
Jun 10, 2017:
- 5:31 PM Ticket #3556 (Run, RunWait and similar calls fail with large amounts of data) updated by
- It appears I am incorrect in indicating Run() itself is the problem. I have discovered what causes the symptoms described above. Immediately prior to the Run() command I have a Progress meter: […] If I remove this Progress() the Run() command works and I collect 750+ bytes without a problem. When I reinstate Progress()the subsequent Run() fails. So the bug is clearly some interaction between the two calls.
- 4:37 PM Ticket #3556 (Run, RunWait and similar calls fail with large amounts of data) created by
- I use Run() with small amounts of STDIO data and it works fine. …
Jun 1, 2017:
- 8:28 PM Ticket #3555 (_GUICtrlRichEdit_StreamToVar with > 2048 characters) updated by
-
Description changed
- 8:26 PM Ticket #3277 (_IEFrameGetObjByName crashes Script after many uses on Win7 and newest ...) updated by
- Tested it with version v3.3.12.0, it does not happen there.
- 8:25 PM Ticket #3277 (_IEFrameGetObjByName crashes Script after many uses on Win7 and newest ...) updated by
- I can confirm that an Win 7 v3.3.14.2 exits with the same error as above. When using an own Error Handler as proposed I get this output: : ==> COM Error intercepted ! err.number is: 0x80020008 err.windescription: Bad variable type. err.description is: err.source is: err.helpfile is: err.helpcontext is: err.lastdllerror is: 0 err.scriptline is: 1811 err.retcode is: 0x00000000 : ==> COM Error intercepted ! err.number is: 0x80020008 err.windescription: Bad variable type. err.description is: err.source is: err.helpfile is: err.helpcontext is: err.lastdllerror is: 0 err.scriptline is: 1811 err.retcode is: 0x00000000 : ==> COM Error intercepted ! err.number is: 0x000000A9 err.windescription: Variable is not of type 'Object'. err.description is: err.source is: err.helpfile is: err.helpcontext is: err.lastdllerror is: 0 err.scriptline is: 152 err.retcode is: 0x00000000 : ==> COM Error intercepted ! err.number is: 0x80020008 err.windescription: Bad variable type. err.description is: err.source is: err.helpfile is: err.helpcontext is: err.lastdllerror is: 0 err.scriptline is: 1811 err.retcode is: 0x00000000 : ==> COM Error intercepted ! err.number is: 0x80020008 err.windescription: Bad variable type. err.description is: err.source is: err.helpfile is: err.helpcontext is: err.lastdllerror is: 0 err.scriptline is: 1811 err.retcode is: 0x00000000 : ==> COM Error intercepted ! err.number is: 0x000000A9 err.windescription: Variable is not of type 'Object'. err.description is: err.source is: err.helpfile is: err.helpcontext is: err.lastdllerror is: 0 err.scriptline is: 193 err.retcode is: 0x00000000
- 2:56 PM Ticket #3555 (_GUICtrlRichEdit_StreamToVar with > 2048 characters) updated by
- […] I didn't realize the editor messed up my code a bit. This should be better.
- 2:53 PM Ticket #3555 (_GUICtrlRichEdit_StreamToVar with > 2048 characters) created by
- This bug was discussed and solved here: …
May 31, 2017:
- 4:17 AM Ticket #3554 (Ini functions should be documentated as containing limitations) updated by
- I'm fairly certain that the only limitation on reading an INI file is in reading a whole section, not the names of the sections. The limitation is already in the help file for IniReadSection. There's also another limitation in INI files that they're supposedly only capable of holding around 38K of data. INF files are not INI files, although they're formatted alike. INI files have no structure other than sections and key/value pairs. INF files are used for installing software or drivers and have a set structure.
May 30, 2017:
- 3:05 AM Ticket #3217 (FileInstall() memory leak) closed by
- No Bug: No new feedback from the original poster, so I'm going to assume that the explanation given fits his criteria. I see no bug.
- 3:01 AM Ticket #3545 (Incorrect conversion of Pos to Rect and vice versa) closed by
- No Bug
May 28, 2017:
- 8:56 PM Ticket #3552 (SciTE 3.7.3 bug: #Region & #EndRegion not working properly when it ...) updated by
- Lines starting with an # are ingnored by AutoIt3, so let's not make this more complex as it is. My reply merely stated why things are happening as experienced and didn't want to have/start a debate on code formatting in TRAC. :) Jos
- 8:17 PM Ticket #3552 (SciTE 3.7.3 bug: #Region & #EndRegion not working properly when it ...) updated by
- Try this: […] You will get: […] I know this is rather this case: […] But this is very strange to write anything else than Case in first line just after Switch. You must to agree with me that in this scenario #Region and #EndRegion are on different FoldingLevel. Also in this case: […] #Region and #EndRegion are on different Folding level and this could not be taken any way, this is just irrational. For me this is the same case: […] This is the same problem - different Folding Level. Would you accept this as a properly written code ?
- 7:52 PM Ticket #3552 (SciTE 3.7.3 bug: #Region & #EndRegion not working properly when it ...) updated by
- I would say there is basically nothing wrong with using it like that, but you need to remember that SciTE only does basic lexing and not syntax interpretation. In this case the Case statement will Close the previous Fold Header ( being a #region) en start a new Fold level, since that is what is needed for a Case line. So it is not a bug but agree it looks strange. Jos
- 6:58 PM Ticket #3552 (SciTE 3.7.3 bug: #Region & #EndRegion not working properly when it ...) closed by
- No Bug: This is a wrong use of AutoIt "syntax", and philosophies. Your region ranges are poorly defined. You can not, write anything between Switch and first Case, this just do not make any sense. I do not see any logic in this way of use Switch...Case...EndSwitch++#Region/#EndRegion Here are examples of proper way showing how to use #Region in this case: […] btw. Personally I prefer this kind of code descriptions: […]
- 6:00 PM Ticket #3554 (Ini functions should be documentated as containing limitations) updated by
-
Version changed
Automatic ticket cleanup. - 5:28 PM Ticket #3554 (Ini functions should be documentated as containing limitations) created by
- There's an old feature request #15 about fixing the various …[…]
- 3:52 PM Ticket #1814 (On InputBox, the language of buttons stays in English) updated by
- I've implemented it based on the latest AU3 source code I could find on GitHub, and following Jon's instructions for code submission. It takes the "OK"/"Cancel" button from Windows standard strings (same way Windows translates the buttons on message boxes). Here's a screen shot on a Portuguese machine: [[Image(...)]] Hope it's appreciated :)
Note:
See TracTimeline
for information about the timeline view.
