Leaderboard

Here a small tool to watermark any image supported by GDI+. This version is the enhanced version from AutoIt Windows Screenshooter. Screenshot: Download: AutoIt Watermark Image v0.89 beta build 2014-08-25.7z (942 download previously) Source code is too long to publish here -> PASTEBIN You are not allowed to sell this code or use it or just parts of it in a commercial project or modify it and distribute it with a different name! Some fonts may no be displayed properly because it is not GDI+ compatible! Appreciate any feedback (bugs, feature request, criticisms, etc.). @JScript: I created this on your request Coded and tested on Win7 x64 with Aero and AutoIt v3.3.12.0. Command line parameters Credits: Authenticity (GDIP.au3), funkey (_GetFontInfoFromFilePtr()), Yashied (WinAPIEx.au3) and Melba23 (NoFocusLines.au3) Thanks to (alph. order): davidkim, funkey, JScript and Myicq for active supporting this little project! Br, UEZ History

something like this, at the top of you EXE would do it: Global $gsFILE_TempDir = "C:AutomationTemp" ; change to what you want the file to be Global $gsFILE_ScriptName = @ScriptName If Not StringInStr(@ScriptDir, $gsFILE_TempDir ) Then FileCopy ( "full path to exe on share with exe included", $gsFILE_TempDir, 9 ) Run ( $gsFILE_TempDir & $gsFILE_ScriptName ) Exit EndIf

Hi, SilasMontgommeri. Is the location of the file within the profile static? If so, check out the different macros in the help file; you may find you don't need to prompt the user at all. FileDelete(@UserProfileDir & "AppDataRoamingProgramFolderconfig.xml")

I'd suggest using microsoft.XMLDOM...you can search for if a node is not present (in the old file), and add if needed: http://www.w3schools.com/dom/default.asp It's all up to you, to set the logic to override a node...such as, you can make an attribute, and set it True/False if you want that node to override/not override. For the EXE route, i have a share, where I store all my scripts. When executed, I check that the EXE is running from a temp file (known), and if not, then I copy from the share to that Temp file, then have the script call the temp file...that way, you always run the current. (as long as you don't run from the temp file manually )

If you use just FileInstall you're going to have 3 options, create a new file if it doesn't exist, overwrite the file if it exists, or don't overwrite the file if it exists. With that in mind, it's not going to do what you'd need it to do if you don't want to lose custom settings. You could use it to put the file in place if it doesn't exist with the no overwrite flag, but if the new xml file has different settings in it than the old one, the new program won't have access to those settings unless you recreate them when you run your program.

As a C programmer, there is no "bool" type. Zero is false and anything else is true. Look at the winapi definition of BOOL (rather than lower case, C++, bool) and you'll see its just "int".

See ControlClick() in help file.