DonationCoder.com Software > LaunchBar Commander

Open using default program eg .doc

<< < (2/2)

Toolbar:
Sorry ... I've only just noticed that the .doc's, although they were opening in Explorer ... the icon is also white there.  Very odd.
This means that LC is now doing the same as Explorer - opening .doc's but icon missing.

If I find out what's happening, I'll report back.

mouser:
Yeah that makes me think that perhaps the file association is working -- but not set up perfectly correctly?

Toolbar:
Hello Mouser
I did try a few things to get the file association working last week and gave up, deciding the solution would show itself at some point - it was no big deal.

All of a sudden, I'm happy to report that the file association is now working in both Explorer and LBC.
Why ? No idea.  It didn't work last night, but this morning it does. 
There hasn't been a Windows update of any sort for several days, but something has started working.

LBC is now looking good.  :)
There will be lots of people who have used Microsoft Office Toolbar from 1997 or 2000 who suddenly find that it doesn't work in W10.
LBC is the best alternative (actually the only alternative) that I've found, albeit more awkward to set up but much more powerful, of course.

mouser:
Thanks for reporting back.
And I'm glad it's useful to you!
Let me know if you think of features worth adding.

IainB:
@mouser: That's interesting.
I had been having a similar problem, but it was regarding running a VBS file. The file had just one line in it. It worked repeatedly just fine, if triggered (double-click) as a .VBS file from Windows Explorer or xplorer² and if triggered via a shortcut from either of those. However, it wouldn't run at all from LBC or FARR - kept giving this error in both cases:



So, I did as you suggested above, re LBC:
...Can n you try this: Go to the topmost "Options" tab and change the setting you have for "Use file launch helper" -- see if that makes a difference?
-mouser (September 06, 2018, 09:45 AM)
--- End quote ---
That setting was empty (not ticked), so I ticked it, and now the script works just fine when triggered in LBC. I realise (from the Options tip in LBC) that changing that option might enable or disable effective triggering of other files via LBC (depending on other factors), so I shall see what transpires, but at least I now know how to enable the .VBS file to be triggered via LBC, so, thankyou.
EDIT: That setting in LBC seems to be not sticky, unless the user Exits LBC nicely and then restarts it.

Now all I need to figure out is how to enable the trigger via FARR ...     :o
Any ideas?

Navigation

[0] Message Index

[*] Previous page