Quıcĸsıɩⅴεʀ 1.3.0 problems

45 views
Skip to first unread message

1.61803

unread,
Aug 10, 2015, 3:36:12 PM8/10/15
to Quicksilver
1. When I launched it it took 90-240% CPU (reading from Activity Monitor), every time, even after clearing caches.

2. Searching was slow and CPU intensive compared to 1.2.0, around 2.5-3.5" for most queries, I had no external volumes during tests.

3. Gesture to close a window of Jitouch (⌘W) kept activating QS, this goes back to 1.2.2.

4. Symlinks broke catalogue scanning, this also goes back to 1.2.2.

Has anyone seen these problems? Do the devs want me to file any of these in the tracker?

I'm on OS X 10.8.5 and now restored QS 1.2.0.

Patrick Robertson

unread,
Aug 10, 2015, 6:25:31 PM8/10/15
to blacktree-...@googlegroups.com
Quicksilver 1.3 requires 10.9+
Stick to v1.2 if you're on 10.8.5 (which is no longer supported)
--
You received this message because you are subscribed to the Google Groups "Quicksilver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blacktree-quicks...@googlegroups.com.
To post to this group, send email to blacktree-...@googlegroups.com.
Visit this group at http://groups.google.com/group/blacktree-quicksilver.
For more options, visit https://groups.google.com/d/optout.

Rob McBroom

unread,
Aug 10, 2015, 9:03:33 PM8/10/15
to blacktree-...@googlegroups.com
On 10 Aug 2015, at 18:25, Patrick Robertson wrote:

> Quicksilver 1.3 requires 10.9+
> Stick to v1.2 if you're on 10.8.5 (which is no longer supported)

Right. It shouldn’t have been advertised to users on 10.8. Let us know
if it was.

--
Rob McBroom
http://www.skurfer.com/

1.61803

unread,
Aug 11, 2015, 4:03:57 AM8/11/15
to Quicksilver, mailin...@skurfer.com
On Tuesday, August 11, 2015 at 3:03:33 AM UTC+2, Rob McBroom wrote:
On 10 Aug 2015, at 18:25, Patrick Robertson wrote:
> Quicksilver 1.3 requires 10.9+
> Stick to v1.2 if you're on 10.8.5 (which is no longer supported)
Right. It shouldn’t have been advertised to users on 10.8. Let us know
if it was.

I asked here, but didn't get an answer, so I just gave it a try.

I downloaded 1.3.0 from the website, didn't checked for updates from the application itself.

You might want to update the download page and changelog.

Is dropping support for 10.8 a developers decision or would the source eventually compile and work in ML? 

Rob McBroom

unread,
Aug 12, 2015, 12:15:25 PM8/12/15
to Quicksilver
On 11 Aug 2015, at 4:03, 1.61803 wrote:

> You might want to update the download page and changelog.

We did update the download page. You said it yourself in the other
thread: Mountain Lion isn’t listed for 1.3.0.

> Is dropping support for 10.8 a developers decision or would the source
> eventually compile and work in ML?

Our general policy is always to support the current OS and the one
before it, but we never drop an OS just because we can.

I don’t remember anything specific that requires 10.9+. If you built
from the current source on 10.8, it would probably work. We’ve just
seen that plug-ins built on 10.10 don’t work on 10.8, so it’s safe
to assume the same is true for an application built on 10.10. That’s
the only reason we don’t claim support for 10.8.

1.61803

unread,
Aug 12, 2015, 5:05:08 PM8/12/15
to Quicksilver, mailin...@skurfer.com
On Wednesday, August 12, 2015 at 6:15:25 PM UTC+2, Rob McBroom wrote:
We did update the download page.

The download page doesn't mention Mountain Lion anymore, not even on 1.2.0, but you can see its icon above 1.3.0. Also, the changelog doesn't mention that 1.3.0 requires 10.9+.

I don’t remember anything specific that requires 10.9+. If you built from the current source on 10.8, it would probably work.

Ok, I might give it a try, although some things I mentioned in my first post were broken in 1.2.2 and don't seem to have been fixed later. 
Reply all
Reply to author
Forward
0 new messages