So after posting I had very odd behavior. Somehow my control-command-a trigger started bringing up lots of different things, opening Terminal.app, flashing various other app windows, etc. Never really saw anything like it. I looked in the triggers.plist to look for corruption but nothing obvious jumped out.

I left it alone for a while and went back to it today. I'm now using rooSwitch to switch between config files for B54 and B56a7. I have cleaned out my ~/Library/Caches/Quicksilver/ folder and tried again. I still find that while I can run this script from a command window, my trigger doesn't run, I see nothing happen.

I do see the following error in Console when I try running the trigger:
Oct 18 13:05:25 Mirisch Quicksilver[3722]: error {\n NSAppleScriptErrorNumber = -1750;\n} Oct 18 13:05:25 Mirisch Quicksilver[3722]: HIToolbox: ignoring exception '*** -[NSURL initFileURLWithPath:]: nil string parameter' that raised inside Carbon event dispatch

There are also many more errors printed by B56a7. and lots of things looking like: Oct 18 12:46:46 Mirisch Quicksilver[3654]: Failed to unregister hot key {\n Key Combination: ,\n Enabled: no\n Key Press Selector: (null) \n Key Release Selector: (null)\n}

I also find that the trigger is not properly saved on restart, instead it looks like this:

<<inline: Picture 5.png>>




I definitely seem to be hitting some trigger corruption issue with B56a7. I've verified that all my other (active) triggers work, though I do see issues with the names of some and I can't rename triggers (by editing in the name box at the top of the info drawer). I'm quite certain that I have all the necessary plugins for all my triggers.

Are there known Trigger corruption issues with B56a7 or is this likely just something on my machine?

Howard

On Oct 16, 2009, at 9:24 PM, AppleScript wrote:


It works for me. I set up the same trigger and tried both the
locations:
~/Library/Scripts/ &
~/Library/Applications Support/Quiksilver/Actions
I am using QS B54(3815) and Leopard. One of the users did complain
that he had problem with the Run action while setting up a trigger in
B56a7. So I suggested him an alternative. See http://u.nu/62jj3 Make
sure that is not the case with you.

As an alternative, I have uploaded the service with instructions in
the "Files" sections.

On Oct 17, 2:32 am, Howard Melman <[email protected]> wrote:
I tried this and while it works when run from a QS command window, it
doesn't work when run from a trigger:

 Picture 5.png
63KViewDownload



On Oct 16, 2009, at 4:28 AM, AppleScript wrote:

Current Web page, Paste:
For Safari:

tell application "System Events"
   set {name:theApp, bundle identifier:theIdentifier} to (get 1st
application process whose frontmost is true)
end tell
tell application "Safari"
           if (count windows) > 1 then
set browserWindow to (first window whose name is not "Downloads")
           else
                   set browserWindow to window 1
           end if
           set theURL to URL of current tab of browserWindow
   end tell
tell application "System Events"
   tell process theApp
           delay 0.2
           keystroke theURL
   end tell
end tell

Reply via email to