Re: Clicking a Growl notification no longer takes me to app (v2.0)

[Daniel Siemer]

One of the things that we had to drop in 2.0 to support sandboxing was
click feedback to apps using older frameworks (1.3 and 1.3.1 framework
should work, and it was tested, but there were some reports of oddness
that we could not reproduce). You can use Growl Version Detective
here: http://growl.cachefly.net/Growl%20Version%20Detective1.2.2.app.zip
to check and upgrade apps to the 2.0 framework. Note that this won't
upgrade app store apps, or other apps which we don't have permission
to touch.

On Sep 20, 9:55 am, Steven Carver <steve19...@gmail.com> wrote:
> So, I upgraded to 2.0 last night to try the Notification Center
> integration, and that's a big mess, so whatever. I am having another
> problem in the mean time.
>
> When listening to Spotify, the Growl notification shows the currently
> playing track, which is exactly what I want. What usually happens when I
> click on that notification, it brings Spotify into focus. The same happens
> to Notify, the now abandoned mail notifier. When I click it's
> notifications, my web browser should open my web mail. Neither of these
> things work. Also, when I get a change to my Dropbox, and I click the
> notification, the proper application function doesn't launch.
>
> These things are incredibly important to me. Have any tips to fix this?
>
> I am using Growl 2.0, on Mac OS X 10.8.2. Thanks for the help.

[Christopher Forsythe]

Did Daniel's explanation not help?

On Thu, Sep 20, 2012 at 11:29 AM, Red Rock Lobster <redrock...@gmail.com> wrote:

I'm having the same issue with other applications. Click Throughs do not work.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/E2ehhKL55X8J.

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

--
Chris Forsythe

@The_Tick

[Red Rock Lobster]

On Thursday, September 20, 2012 1:00:41 PM UTC-4, Christopher Forsythe wrote:

Did Daniel's explanation not help?

Thanks, sorry, didn't see the reply. Not used to Google Groups. I've got other more pressing issues I thought I posted but haven't shown up yet here.

 

[Red Rock Lobster]

Even when an app has been upgraded to the 2.0 framework, there is a new problem with click through notifications.

They work fine when they are first displayed, but after some unknown period of time, they no longer work.  For sure, if the screen saver has been activated since the notification was displayed, they do not work.

[Daniel Siemer]

The old method for click feedback was using NSDistributedNotifications, which we could fire at any time, but these are not allowed under sandboxing with a payload (the context that we send back to the app would know what the click was in relation to).  The new system uses GNTP networking, and eventually we have to close that socket, or we run into the problems that 1.3.x and 1.4 had with running out of socket slots and pegging a CPU, we do this after the display times out or 15 seconds, whichever comes first.  We have plans on improving this, but we haven't gotten that far yet.

[Red Rock Lobster]

Thanks again for the explanation – which I get the spirit of but not the details.  What can I do but rant against sandboxing? Apple may consider these things security features, but they are huge irritations. I feel like my whole experience as a user has gotten worse over the years.

I have use for these click thrus all the time, and they're usually with stay-on-screen notifications, and I usually don't act on them within 15 seconds. I hope this can get "improved".