LBC should resolve environment variables in .lnk files

[Ric0la]

Hi all

Just tried LBC and started to love it, but there's one little glitch which keeps me from using it. In our company, we're developing software for corporate customers, which we sometimes also manage. I've got plenty of ".lnk" files which are generated to access these off site systems in different ways: Putty, SFTP, application GUI etc. The generated links make heavy use of environment variables to allow all employees use the same files. Example target content (Putty):

Code

"C:\Program Files (x86)\PuTTY\putty.exe" -load %NCPROF% -ssh %NCUSER%@xxx.xxx.xxx.com -i "%XCK%\keys\%NCUSER%.ppk" -X

Now LBC ignores this and sends the variables clear text, which of course messes up things.

Any chance this gets implemented? Could be a no brainer, but it doesn't have to ... 

Cheers

Rico

[mouser]

Can you elaborate a little bit about what function you are using where LBC is dealing with the .lnk files incorrectly?
There are several places in the program where LBC deals with .LNK files -- sometimes it copies their properties, sometimes it launches them directly, etc.  I'd like to know which cases you are using.

[Ric0la]

Hi mouser

Sure, sorry I wasn't really clear on that. I'm only using directory folder nodes, two of them. That's it. I created two of them, they're pointing to the root folder of my structure. Nothing fancy.

So my screen looks like:

Code

Options
File myfile.mcf
-- Dock
---- Folder
---- Folder

Cheers

Rico

[mouser]

So your using a node on LBC that shows the contents of a folder, and when you click a .lnk file in the directory contents menu shown, it doesn't replace the environmental variables in those links properly?

[mouser]

Can you try this beta and see how it works:

• http://www.donationcoder.com/Software/Mouser/LaunchBarCommander/downloads/beta/LaunchBarCommanderSetup.exe
• http://www.donationcoder.com/Software/Mouser/LaunchBarCommander/downloads/beta/LaunchBarCommanderPortable.zip

(There are actually two ways I could handle this -- resolve the environmental variables in the .LNK files, or launch the .LNK files directly; this version tries the latter in this case, but I could also try the former method.  Let's try this one first).

[Ric0la]

Works perfectly fine, thanks! I only tried one of the links, I'll keep you posted when I come across something that doesn't work!

[mouser]

Great, when we get a chance we might try the alternative approach and see how it compares.