Thanks for the quick replies.  I had been to the build page of the
wiki, and i probably followed those instructions at first, but don't
think i was following them every time I cleaned out all of my QS files
to try again.

I followed the steps exactly after clearing out all of the files and
directories I listed above and my build worked.  I was able to launch
QA and use my hotkey, the breakpoints i had set up a few days ago when
my journey began tripped as i used the button i wanted to take a look
at.  Thanks a lot!


I'm not sure if it's interesting or not, but both of you asked me to
look at the stop sign to see if it was lit up or grayed out, and Rob
you mentioned that I should have been able to bring up the main window
by clicking the icon in the dock. When i was having my issue, the stop
light was not grayed out.  When I tried clicking the QS icon in the
dock, it did not bring up the main window, all I got was the same
"error" sound that pressing the hotkey resulted in.  I ran "ps -ef"
from the terminal and quicksilver was running from /tmp/QS, then i
checked top and Quicksilver was using 0.0% of the CPU. It didn't seem
to be stuck in a loop or anything, just totally not responding.

Also, I was looking in the console and there was a big difference in
the output.  All I saw when my bad version was running was:

Loading program into debugger…
sharedlibrary apply-load-rules all
Program loaded.
run
[Switching to process 26995]
Running…

but after my rebuild, the working version looked like this:

Loading program into debugger…
sharedlibrary apply-load-rules all
Program loaded.
run
[Switching to process 28554]
Running…
2011-04-13 23:04:43.974 Quicksilver[28554:a0f] Prevented load of
unidentified action from bundle Core Support.qsplugin because the
action's featureLevel (set from its Info.plist) is higher than NSApp's
current featureLevel. This is not neccessarily an error. Sometimes
this mechanism is used to prevent unstable actions from loading.
<<<repeated many times>>>
2011-04-13 23:04:44.304 Quicksilver[28554:a0f] Unknown class
QSUndraggableWebView in Interface Builder file at path /private/tmp/QS/
build/Debug/Quicksilver.app/Contents/Resources/QSSetupAssistant.nib.
2011-04-13 23:04:44.311 Quicksilver[28554:a0f] Unknown class
QSUndraggableWebView in Interface Builder file at path /private/tmp/QS/
build/Debug/Quicksilver.app/Contents/Resources/QSSetupAssistant.nib.
2011-04-13 23:04:51.129 Quicksilver[28554:a0f] Fetching plugin data
from http://qs0.blacktree.com/quicksilver/plugins/plugininfo.php?qsversion=14401
2011-04-13 23:04:52.615 Quicksilver[28554:a0f] Downloaded info for 98
plug-in(s)




Thanks again for your help


On Apr 13, 9:51 pm, Rob McBroom <[email protected]> wrote:
> On Apr 13, 2011, at 7:03 PM, drew lipiecki wrote:
>
> > I'm new to OSX and Objective C development.  I started using
> > Quicksilver based on a few Lifehacker posts i read and so far I like
> > it a lot.  I saw it was an open source product and thought that
> > investigating some of the issues would be a good way to learn the
> > language.
>
> Way to start in the deep end. :)
>
> > I started tracing through the code but when i tried to add some
> > breakpoints and run the code in the debugger i ran into a problem.  I
> > get the QS program to run, it shows up in my dock, but i the
> > activation key [control+space] doesn't bring up the quicksilver
> > window.
>
> With the default setup (which you should have since you’ve wiped everything 
> out), clicking the Dock icon should bring the interface up the same as if you 
> had hit the hotkey. If that doesn’t work, maybe the Application is hung. When 
> you Build and Run or Build and Debug, the stop sign should be lit up. Like it 
> says in the wiki, this should only be a problem if you hide the Dock icon 
> (not default) and only on the first build.
>
> If clicking the Dock icon works, maybe something else on your system is using 
> that shortcut?
>
> > I'm convinced i'm doing some stupid.
>
> Welcome to the club. I feel like a monkey flying the space shuttle with my 
> teeth when I use the debugger, but even I have managed to accomplish a lot 
> with it. It’s a great tool.
>
> Also, there’s a dev list you might want to join.
>
> [email protected]
>
> --
> Rob McBroom
> <http://www.skurfer.com/>

Reply via email to