avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 17, 2018, 01:26 AM
  • Proudly celebrating 13 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - dav4is [ switch to compact view ]

Pages: [1]
LaunchBar Commander / Re: Another LBC bug?: Wrong process started
« on: January 29, 2013, 06:06 PM »
Don't forget this one, too: http://www.donationc...ex.php?topic=31656.0
Closely related.

LaunchBar Commander / Re: bug? LBC fails to set starting directory
« on: January 29, 2013, 07:47 AM »

LaunchBar Commander / Re: Another LBC bug?: Wrong process started
« on: January 29, 2013, 07:33 AM »
This problem still not fixed in v.133.  :(

LaunchBar Commander / Another LBC bug?: Wrong process started
« on: July 19, 2012, 10:56 AM »
When a context menu (for a linked file) lists a number of processes, it seems that the first is always the one started, not the default. In the illustration, the default is to build, but LBC activates the edit.

I'll check and fix; I want to release an LBC update this week so this is just one more thing to fix for it.  :up:

LaunchBar Commander / bug? LBC fails to set starting directory
« on: July 16, 2012, 05:53 PM »
A shortcut placed on a LBC dock behaves differently from the same shortcut placed on my desktop.
The key is that LBC is not setting the "Starts in" properly, as coded in the link. In each case below the Starts in is coded: %USERPROFILE%\publishing\RW (as shown in the Properties of the lnk file). The shortcut invokes a Rexx script that executes the DIR command to show the starting directory.

Running the DIR command from outside LBC shows that the starting directory is properly set. Running from a LBC dock, the starting directory is set to C:\Program Files (x86)\LaunchBarCommander. This causes my application to fail.

Yes, I could change the script to set the directory, but I have hundreds of these, and I think LBC should do its job properly.

Using LBC 1.132.01
Windows 7, 64-bit

Pages: [1]