1. QS is pretty smooth for me
2. I don't use the shelf, but know others are having this problem.
There is a workaround and apparently it's not that bad.
3. I fixed large type in the last build ;)
4. Don't use service so don't know :/ I need to start!
5. Don't know

6. -- don't ask me
7. There have been posts on the internet with b56 not working on SL,
so users having to download b54 which apparently does work

e.g. 
http://www.appledoes.com/quicksilver-and-snow-leopard-finally-work-hand-in-hand.html

I like the idea of having a section saying what does / doesn't work
with each OS. We'll try and get that on the 'new' site.

Long live QS!

Patrick

On Nov 18, 8:58 pm, Hagure <[email protected]> wrote:
> Forgive me if I'm covering old ground.
>
> I'm thinking of upgrading to Snow Leopard since 10.6.2 is out. The
> only thing holding me back is how well QS works with it. As we all
> know, a computer w/o QS is simply a glorified calculator!
>
> I follow the group through email (yes, I agree a new/revamped site is
> necessary), but haven't found a solid report on what works and what is
> broken with the recent builds. I know Etienne/Tiennou has just
> released a new build that fixes some of the SL compatibility problems
> that people were having.
>
> What I've managed to gather so far:
>
> * QS in general runs smoothly with 10.6.2
> * QS Shelf appears randomly
> * Large Type Action doesn't work (not sure if this is true for 3840)
> * Triggers DO work properly with the latest build
> * Service Menu item/Send to QuickSilver functionality works/is
> possible
> * Service Menu plugin no longer works, but functionality can be
> replicated through scripting
>
> Questions I have:
>
> * What else (if anything) is broken/wonky? Personally, I'm most
> interested about the "Current ___" Objects
> * Does anyone use b54 (alcor's last build), if possible at all?
>
> I haven't really been engaged in QS discussion since the move to
> Groups, and would like to take this opportunity to jump back in. Yes,
> source repository issue tracking tells us what doesn't work, but it
> doesn't tell us what DOES. My main goal here is to have a single,
> simple list that allows people (especially those like me who haven't
> been keeping up with the builds) to quickly see what works and doesn't
> work. It could be sectioned off by OS version too.
>
> Thanks for yall's help and continued dedication towards keeping the
> Best Application alive!

Reply via email to