Welcome to QS!
I pretty much learnt all I know about Cocoa/Objective C through bug fixing
for Quicksilver and writing plugins :)

As long as you've done everything in the list here:

http://qsapp.com/wiki/Building_Quicksilver

then it should work. The points at the bottom of that page are important,
and may be your problem.
Just make sure you're
a) building correctly (See above)
b) are in debug mode
c) Checking the console (Run -> Console) for any information

I think it may be something to do with what's described at the bottom of the
above page

On 14 April 2011 09:03, drew lipiecki <[email protected]> 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.
>
> 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.
>
> I've spent a few days searching this group and trying some things but
> I've had no luck.
>
> i have removed different combinations of the following directories/
> files as i found them mentioned in different posts:
> /tmp/QS
> /Applications/Quicksilver.app
> /home/{user}/Library/Application Support/Quicksilver
> /home/{user}/Caches/com.blacktree.Quicksilver
> /home/{user}/Caches/Quicksilver
> /home/{user}/Caches/Preferences/com.blacktree.Quicksilver.plist
>
>
> when i removed all of the above directories and rebuilt and ran
> quicksilver from the debugger i went through the first run install
> process, but i still couldn't use the activation key sequence to bring
> up with main window.
>
> I'm convinced i'm doing some stupid.  If anyone could give me a
> suggestion or point me to a link for an earlier discussion i'd really
> appreciate it.
>
> thanks

Reply via email to