Unfortunately, the number of NSAutoreleaseNoPool() errors swamped 
everything else to the point where they pushed the other errors off the 
console messages window completely.  I caught a few glimpses of other 
errors while working, but never got to read any of them.

At any rate, I caught and fixed errors the lazy way and have a working 
script (attached).



On Monday, July 30, 2012 12:59:47 PM UTC-5, Rob McBroom wrote:
>
> On Jul 30, 2012, at 1:47 PM, Christopher Harwood wrote:
>
> I am having some difficulty with an Applescript that works on Finder 
> selections but does not work as a second-pane action on QS selections. 
>  I've attached both scripts here, and I'm sure there is a lot of room for 
> improvement in both, but my primary question is: How do I get error 
> information when QS action script fails?  Does QS keep an error log, or 
> should I just watch the console?
>
>
> The console is pretty much it. Though I think there are system-wide 
> debugging settings for AppleScript that crank up the amount of stuff it 
> logs (still to the console) regardless of how it's being called, so you 
> might try that.
>
> -- 
> Rob McBroom
> <http://www.skurfer.com/>
>  
>

-- You received this message because you are subscribed to the Google Groups 
Quicksilver group. To post to this group, send email to 
[email protected]. To unsubscribe from this group, send 
email to [email protected]. For more options, 
visit this group at 
https://groups.google.com/d/forum/blacktree-quicksilver?hl=en

Attachment: Count To Do Items (QS).scpt
Description: Binary data

Reply via email to