bytejnr.blogg.se - Download ntwind hstart

Reg Script Use a Registry Script such as following to create a right-click menu entry for LnkEditorGUI for. lnk file right-click context menu registry association example below). A command line argument is accepted and the GUI will automatically open the first file passed to it as an argument allowing for easy association on the right-click menu (see. A nice and big (and resizable) GUI is presented with which the user can easily edit and create LNK shortcuts with. This GUI uses built-in AutoIt functions FileGetShortcut() and FileCreateShortcut() to read and write. Solution: LNKEditorGUI is a resizable and easy to use creator and editor of LNK Windows Shortcut files. Very often you need to create a link with a long path and many arguments which becomes hard to see and make edits.

lnk shortcuts with the Windows dialog is very frustrating due to the small input boxes and non-resizable small dialog window. Hstart is pretty awesome.Scenario: Editing. I tried CHP first and it certainly does what it says it will but I found I wanted the option to wait until the spawned task was finished. However, if there is something suitable around I much prefer to use that.Īfter a quick search I found these two options: And of course you can dig right in and make the function call directly. If you want to go for option 1 in clarion you might like to look into PowerRun from Berthume Software which is available for free download.

Find something that already does this so I don’t have to.

Write a helper DLL that wraps the CreateProcess function and can be easily called by the templates.

There are a few ways to do this but essentially they all seem to revolve around the CreateProcess api Function. Often this is fine, especially for long tasks where it is nice to see the progress but sometimes it is annoying and it would to be nice to be able to hide the window. The thing that is annoying about this is that you will get the command window popping up when the command is run. This works great and has the added advantage of being able to execute, obviously, batches of commands in one go. I decided that the safest way was to write the commands out to a temporary batch file and use #RUN to just call that. Searching the newsgroups there were a few comments from people having similar issues and the symptoms were seemed a little sporadic. I ran into what appeared to be limitations in the length of parameters accepted by the Clarion templates #RUN statement. Recently I have been doing a fair amount of work trying to automate parts of the development process, in particular the version control aspects.