List background opacity

[iandol]

This is pretty minor, but I noticed (using build 400B) that if you set the List background opacity to 0% (Appearance > Colors > Lists), the background is 100% black. I do remember I used to control the opacity for list backgrounds so this has regressed at some point "fairly" recently:

I tested with Nostromo and Bezel.

[skurfer]

Yeah, the opacity seems to be completely ignored. Thanks for pointing it out.

[pjrobertson]

Yuck. It seems like opacity gives funny behaviour all round. If you turn it on for Bezel, then select a couple of different objects, you'll see the old object/actions behind the current one (but only on a white background)

[iandol]

Can confirm for Nostromo too, I still see the faint ghost of the first selection up to about 30% opacity then it disappears (so this 👻 is probably always there even when opacity is 100%)... If I use the comment trick, I still only see the first selection as the ghost... Time to call Ghostbusters? 👻 🔫

[skurfer]

I just tried 400B on my 10.8 VM and the opacity seems to work as expected, and I see the same issues with 1.1.3 under 10.9.

So the issue is probably caused by a change in OS X and not Quicksilver. Of course it still needs to be addressed, but at least we don’t have to go digging to figure out what we changed.

[pjrobertson]

Not sure if opacity has anything to do with CGSPrivate, but it might be a though.

Good idea to test 10.8

On 29 Mai 2014, at 19:47, Rob McBroom notifications@github.com wrote:

I just tried 400B on my 10.8 VM and the opacity seems to work as expected. So the issue is probably caused by a change in OS X and not Quicksilver. Of course it still needs to be addressed, but at least we don’t have to go digging to figure out what we changed.

—
Reply to this email directly or view it on GitHub.

[pjrobertson]

@skurfer just reminded me of this on my new pull request #1877
I'd forgotten about it, but looking at it now, I do remember being really puzzled by a black background for the window. I tried all sorts of things but couldn't change it. At least for the time being I'm inclined to give it a low priority status

[iandol]

Thanks @pjrobertson and @skurfer ! I had an somewhat unrelated question which doesn't warrant a new issue which was whether it would be easy to add a "blur" factor somewhere in QS in addition to the opacity; i.e. some way to emulate Yosemite's everything-is-translucent styling?

[skurfer]

whether it would be easy to add a "blur" factor somewhere in QS

I’ve looked at doing that in Nostromo. It doesn’t appear to be easy. (Not to me anyway.)

[iandol]

The only things I've seen online, seen through the eyes of one who knows not Cocoa nor Obj-C!!!:

http://stackoverflow.com/questions/11174918/how-to-get-window-with-semi-transparent-blurred-background
http://stackoverflow.com/questions/3298490/apply-a-cifilter-background-filter-when-host-window-is-transparent
https://github.com/dsns/GaussianBlur_NSWindow_os_x_mavericks
http://www.cocoanetics.com/2013/10/blurring-views-on-mac/ (only works to blur content, not desktop)
http://cocoasnippets.io/cocoa/ui/nswindow/coregraphics/2014/02/27/translucent-nswindow-with-blurred-background.html

OS X Terminal has a blur feature, I assume using the private API suggested in the stackexchange links. But whether any of this is compatible with how QS creates its window...

[skurfer]

I think it’s possible with Core Animation, but none of the official interfaces use it.