LabVIEW
How to associate a file extension to an executable ?
Solved!
The association of a file extension with an executable is an OS issue. Are you using windows?
It is a simple as clicking the unassociated file, selecting the application, and check "always use this program ...". 🙂
On the LabVIEW side, you need to make sure that your executable reads the commandline options in order to get the name of the clicked file when it opens via this mechanism (e.g. double clicking an associated file, drop a file on the executable, etc.)..
On the diagram, you read the commandline parameters via the "application..comandline arguments" property in the code.
When building the executable, you should ensure that you specify "Pass all command line arguments to application" (it is under Application Settings).
It is a simple as clicking the unassociated file, selecting the application, and check "always use this program ...". 🙂
On the LabVIEW side, you need to make sure that your executable reads the commandline options in order to get the name of the clicked file when it opens via this mechanism (e.g. double clicking an associated file, drop a file on the executable, etc.)..
On the diagram, you read the commandline parameters via the "application..comandline arguments" property in the code.
When building the executable, you should ensure that you specify "Pass all command line arguments to application" (it is under Application Settings).
Here's a quick test executable I made about a year ago (just built again into a 7.1 LV application). The diagram is shown in the image.
Now create a file with a random unused extension, e.g. abc.zzz, double click it, and specify to always open it with commandline.exe.
The first element in the array is the name of the application. the second element is the double-clicked file.
Now create a file with a random unused extension, e.g. abc.zzz, double click it, and specify to always open it with commandline.exe.
The first element in the array is the name of the application. the second element is the double-clicked file.
Message Edited by altenbach on 04-15-2005 11:12 PM
It basically boils down to write the correct entries to the registry. This can be done with a small labview executable that you include with the installer. In the advanced Installer settings you can specify to run it at install time. LabVIEW includes registry access tools (in the advanced palette) that will let you interact with the registry.
@chilly charly wrote:
But how could I do that on a customer's PC ?
I am not very familiar with all the details, so hopefully somebody will chip in.
@chilly charly wrote:
And have you any idea on how to associate a specific icon to the custom files ?
No, but I would like to know how to do that myself. 🙂
A good place to start is microsoft KB article 256986 and the links mentioned in it.
For a better feel, you might just run regedit and browse around in the keys. For example, search for "LabVIEW" and look at all the keys containing it. (Just don't start randomly changing or deleting things ;))
The status bar at the bottom always shows the full key your are currently viewing.
For a better feel, you might just run regedit and browse around in the keys. For example, search for "LabVIEW" and look at all the keys containing it. (Just don't start randomly changing or deleting things ;))
The status bar at the bottom always shows the full key your are currently viewing.
