Context Navigation

Timeline

12:09 PM Ticket #3727 ($VERSION not increased in compiled script with ...) closed by Jos: Fixed

9:23 PM Ticket #3727 ($VERSION not increased in compiled script with ...) updated by Jos: New version available in beta that runs de version update before au3stripper. Please try and let me know whether that solves the issue. Jos
12:04 AM Ticket #3727 ($VERSION not increased in compiled script with ...) updated by mLipok: Owner, Component changed

10:15 PM Ticket #3727 ($VERSION not increased in compiled script with ...) created by Van0: […] With this two lines $VERSION variable automatically updated …

6:56 PM Ticket #2962 (GUICtrlSetImage resizes Pic control with $SS_SUNKEN style) updated by MrCreatoR: 3.3.14.5 the same. 5 years... any chance for a fix?

5:02 PM Ticket #3723 (Odd problem with _GUICtrlRichEdit_ReplaceText) updated by BrewManNH: 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.

3:14 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by BugFix: 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 param3 And, 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 J-Paul Mesnage: 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 BugFix: > 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 J-Paul Mesnage: 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?

12:04 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by BugFix: ".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.

8:50 AM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) updated by J-Paul Mesnage: 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

10:09 AM Ticket #3691 (Wrong link in the CLSID List page) updated by Erix: 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/

5:12 PM Ticket #3726 (_WinAPI_PathGetArgs / _WinAPI_PathRemoveArgs -- using like the help ...) created by BugFix: The help example for the _WinAPI_PathGetArgs and …

Note: See TracTimeline for information about the timeline view.