Timeline
Jul 24, 2019:
- 5:02 PM Ticket #3723 (Odd problem with _GUICtrlRichEdit_ReplaceText) updated by
- Can you post an example script that demonstrates the problem? This way we don't have to reinvent the wheel, and might not be doing it the same way as you are doing it.
Jul 23, 2019:
- 3:14 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by
-
Replying to Jpm:
> So what do you suggest as the examples are correct?
As i wrote in my start post:
> I would recommend using a defined path for the help example, instead of _WinAPI_AssocQueryString.
We could e.g. use these:
AutoIt3.exe myScript.au3 param1 param2 param3And, of course, the indication that paths that contain spaces must be encapsulated in quotes. - 1:10 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by
- So what do you suggest as the examples are correct?
- 9:57 AM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by
- > the examples for all Udf referenced in the examples are correct so what do you want to be improved? That's what they are in the particular case used. But help examples should be universal, or am I wrong? I've made a script in the same manner like the help example. And this gots wrong results. Therefore, I wanted to point out that help examples should be designed so that they can not provide any mistakes.
- 8:17 AM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by
- Are you sayning that ".au3" is not a well formatted. the examples for all Udf referenced in the examples are correct so what do you want to be improved?
Jul 22, 2019:
- 12:04 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by
- ".profile" was just one example. This is common to all programs that create dirty registry entries. For example, the entry for ".gadget" is also incorrect. I just wanted to point out that a function that reads from the registry, can also bring erroneous values and therefore should not be used for a help example.
Jul 20, 2019:
- 8:50 AM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by
- I Don't know how your .profile have been created but for me is a program installer update the registry correctly it must include the path to .exe in quote so for me there is no error In my system the .profile is not created. You can try .xls to verify
Jul 17, 2019:
- 10:09 AM Ticket #3691 (Wrong link in the CLSID List page) updated by
- Ok, why not put a link to an archive of the page, like this one for example : https://web.archive.org/web/20170527141521/http://www.pctools.com/guides/registry/detail/61/
Jul 16, 2019:
- 5:12 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) created by
- The help example for the _WinAPI_PathGetArgs and …
Jul 6, 2019:
- 3:06 PM Ticket #3725 (Regexp POSIX classes description misses some specifications) created by
- In UCP mode the following POSIX classes expand their range: [:space:] …
Jul 4, 2019:
- 1:34 PM Ticket #3724 (_DateTimeSplit should ignore trailing Z (to accept parsing RFC3339 ...) updated by
- Modifying the various date/time functions for full compliance to the RFC would be a huge and difficult task leading to a number of script-breaking changes. Rigourous handling of timestamps is populated by hords of venimous worms, whatever language you use. If your application requires handling anything not covered by the current simple implementation, I'd advise to write a UDF covering a wider range of formats.
Jul 3, 2019:
- 10:00 PM Ticket #3724 (_DateTimeSplit should ignore trailing Z (to accept parsing RFC3339 ...) updated by
-
Version changed
Automatic ticket cleanup. - 9:56 PM Ticket #3724 (_DateTimeSplit should ignore trailing Z (to accept parsing RFC3339 ...) updated by
-
Type changed
This can't be a BUG as the supported formats are clearly defined in the Helpfile. Change it to a feature request. Jos - 8:33 PM Ticket #3724 (_DateTimeSplit should ignore trailing Z (to accept parsing RFC3339 ...) created by
- When passing a RFC3339 formated date-time string to _DateTimeSplit, …
Jun 29, 2019:
- 4:33 PM Ticket #3723 (Odd problem with _GUICtrlRichEdit_ReplaceText) created by
- After months of observing an odd problem when clearing the text in a …
- 3:00 PM Ticket #3704 (_FileWriteToLine docs update for hidden files) updated by
-
Milestone changed
Automatic ticket cleanup. - 2:44 PM Ticket #3704 (_FileWriteToLine docs update for hidden files) updated by
- I checked FileWriteLine, but _FileWriteToLine shows the explained error. Fixed by adding the note to _FileWriteLine.
- 2:42 PM Ticket #3704 (_FileWriteToLine docs update for hidden files) reopened by
- 2:40 PM Ticket #3704 (_FileWriteToLine docs update for hidden files) updated by
-
Owner, Resolution, Milestone changed
Fixed by revision [12219] in version: 3.3.15.1 - 1:50 PM Ticket #3691 (Wrong link in the CLSID List page) closed by
- Wont Fix: The link is just a reference to where the information you find on the page has been taken from. So even when the link no longer works, no information is lost. As the Internet changes permanently (means: even when whe add a correct link to this infomation it won't be stable forever) it is just a minor flaw: Won't be fixed for the time being.
- 1:29 PM Ticket #3703 (2 ^ 49 and further return wrong results) updated by
- Telling us that something is wrong isn't enough. As the wiki states: A ticket "should contain all the information necessary to reproduce the issue". So please provide the expected (correct) result as well.
- 1:20 PM Ticket #3717 (StringFormat doesn't format int64 integers correctly) updated by
- Tested with 3.3.15.0 - same problem.
- 12:40 PM Ticket #3705 (Fixed: Assigning objects by reference to COM properties) closed by
- No Bug
- 12:39 PM Ticket #3705 (Fixed: Assigning objects by reference to COM properties) updated by
- That's correct COM error handling has been reverted as you described.
- 12:33 PM Ticket #3704 (_FileWriteToLine docs update for hidden files) closed by
- No Bug: Tested with AutoIt 3.3.14.5 on Windows 7. The "Hidden" attribute does not prevent writing to a file. Hence: No Bug!
Jun 27, 2019:
- 2:17 PM Ticket #3722 (StdoutRead example is incorrectly parsing input and outputs incomplete ...) closed by
- Fixed: Fixed by revision [12218] in version: 3.3.15.1
- 2:05 PM Ticket #3325 (_Word_DocSaveAs not working with the default $sFileName parameter) updated by
- Fixed by revision [12217] in version: 3.3.15.1
- 2:04 PM Ticket #3325 (_Word_DocSaveAs not working with the default $sFileName parameter) closed by
- Fixed: Fixed by revision [12216] in version: 3.3.15.1
- 11:06 AM Ticket #3722 (StdoutRead example is incorrectly parsing input and outputs incomplete ...) updated by
- I was just making fun of that line because it seems hilariously stupid and complicating to me. Granted I've made stupid mistakes like these too. No bad intention of course :) About that console thing, you're probably right. But I was going with the original settings since there are no specific checks for every single thing that can be changed within AutoIt otherwise the help-file-examples would explode with if-conditions. Anyway, hopefully it will be fixed soon so the example provides a good example again. Thanks for working on it!
- 9:41 AM Ticket #3722 (StdoutRead example is incorrectly parsing input and outputs incomplete ...) updated by
- Replying to anonymous: > I don't know who came up with the wrong line but he must have been on drugs or something. Humans make mistakes ... right? I checked the commits for this file and see that it was changed in Revision 7904 (15/7/2013) which indeed should be reverted. As to your fix: One have to assume that some console applications do not always return @CRLF, but only use @LF, hence was chosen to strip the @CR character and also support programs that only have a @LF as EOL. Jos
Note:
See TracTimeline
for information about the timeline view.
