Very strange, especially since I've been using daily. I changed "$useExtViewer = 0" I got the same result. When I manually deleted the folder along with the chm and then run the script, I get the main script page, but like I said before, I get just a few entries like advance topics and a few symbols. I also loaded a new copy of the script and the exe file incase it was corrupt in some was. A normal run of Help via XY is working fine. I see in the script you use SC delete to delete the folder and the chm. After completion (of the 5 lines), yes everything is there in the ~XY_CHM folder. If I run the last 3 lines which copies XY's chm, changes the directory and decompiles it, everything is fine as far as the looks of the temp folder and its contents, but when I run the script from the catalog it only a has a few items listed on the main page. Evidently when the folder does not exists it gives the error. Also, many times documents open with a 'Read-only', so I have to go into Task Manager and close down the program. The first line (rmdir) throws out the error (same error as shown above). Check the temp environment variable.' I have tried all the suggested cures, but nothing works. Hi highend, I ran the 5 lines in sequence. Update: On the last XY beta v, I ran the ShowHelpTopics and then closed it prior to commencing the update using SimpleUpdater and had no issues. That issue should be corrected in SimpleUpdater (i.e., not to change the ini file unless the update is actually performed, which it wasn't in this case). Of course once that happens, SimpleUpdater performs it's timestamp in the ini file and subsequent attempts aren't allowed because it says or thinks it's up to date. Could it be that "ShowHelpFile.exe" is process is open and keeping XY from being updated? Right now I do my variables check OnDrop, and if it turns out the be an invalid. With ShowHelpTopics v1.1.0, I wasn't abled to continue with the update after closing the help file. temp folder, then Explorer moves them once its done.4. Usually though I can close the help file and continue with the update. As has happened countless times in the past, I've forgotten and had the help file (accessed through the normal means) open when I ran the "SimpleUpdater" script. I experienced an issue when performing an XY update using Simple Updater however. After 'success' appears, you can then use windows explorers address bar to test your newly created variable. SETX VARIABLE 'Variable Destination Path'. May take a moment to process (do not include any in the command). Will display the message "Hi, I'm uncle Ted!".Nice update highend. Creating the environment variable from the cmd prompt will actually work. $name = "Ted" msg "Hi, I'm uncle $name!" Variables are resolved wherever they are found in the arguments of all subsequent commands of the script, even if they are found inside quoted strings for example: The script $a = "Hi!" msg $a will define a new variable $a and assign the string "Hi!" (without the quotes) to it then a message box will display "Hi!". XYplorer allows you to define and use as many variables as you want, using a number of commands like set, input, replace, etc. Now you can use environment variables and XYplorer native variables when stating AllowedDirs and DisallowedDirs. Its command msg "" produces the message box showing the current date.Īdvancing in script writing, you will soon feel the need for variables. In this case the hidden script with the label "_date" is called and executed. The sub command is a special command to call a script inside the same script file. The script with the label "date" will be executed directly. Now run the script load "date.xys", "date". The popup menu will show only two of the four contained scripts. To hide a script simply prefix an underscore to the caption or label (a hidden script does not need a caption anyway).įor example, create a script file "date.xys" in application data path with the following contents: // this is in script file "date.xys" Hidden scripts can be executed but are not shown in the script file's popup menu. Next to the Variable name, type: userprofile Next to Variable value, type: C:Usersusername (Replace username with your username on the computer) Click OK to add the new environment variable. If the above is saved to a file called "test.xys" in application data path then the following command will directly bring you to the System folder: load "test.xys", "system". Navigate to Advanced > Environment Variables. For example: // some little test scripts, using labels The label is attached to the caption, separated by " : " (space-colon-space). Script Files for the Advanced Labelsīy using labels you can execute a script inside a file directly, avoiding the popup menu. You will get an idea of the potential of scripting by now. The existence of a command load, of course, means that one script file can load another.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |