LabVIEW
Registry Items for Custom File Extensions
Solved!
Sorry for waking an old thread, but I've added some more functionality to the custom file extension that I thought would be interesting. Perhaps you're all way ahead of me, but I think it's cool!
Adding windows shell right click menus is very straightforward and different menu items can send different commands to your LabVIEW applications.
Computer\HKEY_CLASSES_ROOT\<extension name>\shell\<RightClickName>:
- (Default) > "What you want to appear in the right click menu"
- Icon > "Exe path or ICO path"
Computer\HKEY_CLASSES_ROOT\<extension name>\shell\<RightClickName>\command:
- (Default) > "Exe path" + Commands to send to application
You can also make cascading/organised menu items by following this guide: https://medium.com/analytics-vidhya/creating-cascading-context-menus-with-the-windows-10-registry-f1...
(then editing the LabVIEW installer to match)
@RavensFan wrote:
@MIG wrote:
By the way, thank you for your tip about the "OS Open Document" event - I had no idea that even existed.
Neither did I. And I can't find anything in the help that explains how it works.
You missed the SuperSecretPrivateSpecialStuff part in the picture of the first post! 😁
And no this is not part of a secret cabal trying to deprive you of a very handy function. The reason it is not public is that this function was added at some point long ago by someone who needed this for an NI tool they created without the necessary testing, test bench torturing, magic incantations and product manager bribery necessary to let a new feature into the released product and has since been long forgotten. 😎
There are likely many things like this that got sneaked into the code by a developer that would have caused more than a lifted eyebrow by the managers and a harsh: "You did spend time on what??????".
