Jump to content

TheDcoder

Active Members
  • Posts

    7,103
  • Joined

  • Days Won

    88

Everything posted by TheDcoder

  1. Wrapper for IniRead. Writes the "default" value to the Ini file if the key does not exist! Very useful to generate config.ini by just replacing IniRead with IniReadWrite P.S Why quote the entire post? Unesseary padding...
  2. 2017's first snippet, let me cut the ribbon with an almost useless piece of code . I present you IniReadWrite, What it does is write the "Default" value to the Ini file if the key does not already exist . Head over to GitHub Gist to grab the snippet, the reasons why I am not posting the code are: Gist has a download feature (which creates a ZIP automatically which includes the code + license). My code would survive any catastrophes like forum upgrades, loss of database etc. Gist is a dedicated service which is a better place for code to be hosted plus I love the git backend .
  3. Are you referring to the output made by the command?
  4. My pleasure .
  5. Maybe have a look at the Best Coding Practices
  6. That is because cmd.exe (command prompt) returned 1 (That means the call actually succeeded). Failure only occurs if the process/command was not able to execute, in this case, the command did execute. _RunDos is just a wrapper for cmd.exe (look at the code yourself). That means cmd.exe was successfully executed and therefore there is no failure here, hope I have cleared your doubt
  7. As far as I remember, AutoIt (the interpreter) stops the execution of the script as soon as it encounters a bug, so there is nothing which can be done after that point by that script. I might be wrong though.
  8. According to the Forum Rules, sharing of scripts which bypass captcha is not allowed.
  9. yeah... real genius . How to remove EVERY virus from your computer: Uninstall Windows.
  10. Thanks for the suggestion @jchd, I have added Red Dragon to my wishlist... I will try reading it one day when I become a C programmer with a beard . I do not want to mess my brain up by reading about compilers, interpreters alone are complex enough for me
  11. I... I don't even understand the sample code in that quote O_o How much $$$?
  12. I guess I do not have the permission to read the story
  13. I see... so you are looking for people who would like to start fresh? or will you be providing the source to the interested candidates? I personally wanted to have a look at it . On a side note: Au3Check is made with AutoIt, am I right? or is it all C++? I am not good at C++ at all
  14. Is Au3Check's source code available?
  15. I don't really have any defence ready for that . I just follow the herd... of sheep Happens
  16. Maybe those people can't think of any better way to do it? ¯\_(ツ)_/¯ They will, of course, find a better way after asking at the forums (Same thing with me) I totally agree with this one. As for my workaround, after taking useful input from here, I decided to separate the GUI #Regions into 2... GUI Creation (functions) at the top and the GUI Event Handlers at the bottom. It works perfectly . Thanks to everyone who participated in this thread!
  17. A great idea actually... I will try this one And yes, I know that #include tells the interpreter to think of the included file as if it has been copied over at the #inlude line
  18. I don't want to move the functions to the top... It's not the place where a function should be. Now I am thinking of changing the style, any recommendations on how should I proceed?
  19. I sincerely apologise for using the word "annoying" but it is/was not my intention to hurt anyone . I am very grateful for the efforts which you have put in the community and I mean it! It is not my intention to sadden anyone, but circumstances force me to use terrible word choices... I am currently looking into possible workarounds, I will shortly reply about my workaround if I find it.
  20. I remember visiting the SciTE help file, did not find anything there... not even #AutoIt3Wrapper_Jump_To_First_Error! I might have missed it, I am not much of a reader but a skimmer
  21. I get you @Jos, we should at least have something by which we can "ignore" some errors. Do you agree with me?
  22. The only thing which bugs me is that SciTE automatically takes the cursor (the blinking position thingy) to the line of the warning... it is quite annoying! The function in which I am declaring the Global variable is supposed to be only called once per execution... so that would not cause any chaos . I would love to do that but I still have to a lot to learn... and the very limiting TIME factor . P.S I see that Jos has replied before I finish this post, will reply to his post in another post.
  23. Yes : I am aware that it is not worth to make it act as an interpreter but it could at least read the function's code if the function is being called.
  24. Hello everyone, I discovered a bug yesterday and I posted it at the bug tracker: I also made a simple script which can be used to reproduce the bug: CreateVariable() ConsoleWrite($sGlobalVariable & @CRLF) Func CreateVariable() Global $sGlobalVariable = "Foobar" EndFunc The bug was closed by @BrewManNH: While I partially agree with the above statement, My code was not practical enough... so @mLipok advised me to create a thread on the forums with practical code (Thanks!). That is the point of this thread, I am going to provide the code where I experience this bug/problem . I discovered this bug when I was working on one of my projects called "ProxAllium". When the main script finishes execution, Au3Check throws a nasty warning about "variable possibly used before declaration": As you can see, the variable is indeed being used after calling the function in which the variable is declared... The warning won't appear if I declare the function ABOVE the variable. As @BrewManNH said, Au3Check reads line by line... I think this should be changed, Au3Check should not throw warnings if the interpreter is able to run the code, at least most of the time anyway! So what do you guys think? Is this a valid bug?... and I request those who participate in the discussion not to discuss the code being "poor", that is another thing/thread in itself P.S I had already written this once but the forum editor decided to mess up and when I undid (Ctrl + Z) something... This is a poorly written version of that article, I was very frustrated while writing this!
×
×
  • Create New...