Growl 2.0 clicking notification visual doesn't take me to the app

[Sulaiman]

Hi, 

I have just recently updated the Growl to 2.0 and i'm having issue with Growl using Mountain Lion and i have noticed that when i clicked the notification (when email arrived in Sparrow and clicked it should redirect to the app behavior in 1.4) it doesn't redirect me to the mail client for example when someone becomes available and Growl responds and shows up the notification and when i click that it takes me to the person whom i clicked, But now it's different when i clicked the notification it doesn't take me and it just stay on desktop.

I would like to go back to Growl 1.4 it's better and works perfectly and how can i get back?

Please let me know and its more importance to me as i have been working on several tasks and only Growl helps me to remind (Likes of Reminder, Task complete, Milestones) of those works! 

Thanks,

S.

[Chris Forsythe]

The way we were doing clicking in 1.3.3 and below doesn't work with sandboxing. So the only solution is to update the framework in the app to 2.0. 

The only way back to 1.4 is to build it yourself.

-- 
Chris Forsythe

@The_Tick

--
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/-/oHHWBSO8BtsJ.
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.

[Sulaiman]

Thanks for your response, I have tried to update the firmware of the app when i updated skype's firmware to 2.0 the chat messages are missing and when i downgraded the firmware the chat messages are appeared back. I think updating the app's firmware may affect some parts,

How can i build the way back to 1.4? is there download link? please help me with it!

[Nikit]

I have the same issue - clicking on the Growl message does nothing at all - I think that broke when I updated to OS X 10.8. 

Any fix in the works?

[Charlie S]

The apps use the growl framework to talk to Growl to display the notifications, the app developer needs to update to the growl framework they use to Growl Framework 2.0 

On Tue, Oct 30, 2012 at 1:55 PM, Serge Malevanny <s.mal...@gmail.com> wrote:

I have the same issue and i want to know if there any way to solve it by myself or it could be fixed in some update of growl? Really miss it, it was the most usable thing in growl for me. 

I don't quite understand your answer about updating framework — what framework and in what app should be updated, could you, please, explain it maybe?  

Thank you. 

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

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.

--


----
Charlie Schloss

Grab Opera the fastest browser on earth @
http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop


Why Open the Web?

Despite the connecting purpose of the Web, it is not entirely open to all of
its users. When used correctly, HTML documents can be displayed across
platforms and devices. However, many devices are excluded access to Web
content.

http://my.opera.com/community/openweb/info/

[Christopher Forsythe]

We've responded, repeatedly on this list, that you can update applications yourself with the Growl Version Detective application that is right on our downloads page. So you can give that a go.

However, this is just how it is. Apple required sandboxing, we've done the best that we can to make Growl work with sandboxing, and unfortunately clicking was using a method that no longer works there. Even if Growl was not in the app store, if an app *is* in the app store they would need to update.

The best solution is to get app developers to update Growl. But like you said some will not, so that's why we have GVD.

I hope this answers your question better.

Chris

On Mon, Nov 5, 2012 at 3:03 PM, Jon Yurek <jyu...@gmail.com> wrote:

No offense, but that sounds like kind of a blowoff answer. Not everything can/has/will update, and that leaves the users of these apps (me included) with their cheese out in the wind.

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

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

[Jon Yurek]

Actually, it does answer it. Thank you.

I apologize that I came off gruff and for not reading deeper, but this was one of the first things I found on google about not being able to click on a notification, and this was what I saw. It would have helped were this answer, or something more specific to clicks not working as they have previously, were added to the FAQ. I see there is a question about apps showing up, but not about clicking on notifications not behaving the same. I searched for info about clicking, found nothing, and continued on. I wouldn't know that was there if I hadn't been prompted to look deeper because of your reply. 

Not trying to be critical here, just describing what I did in the hopes that it might help alleviate future confusion on this point. 

Thanks again. The Version Detector has, indeed, fixed my problem.

[Christopher Forsythe]

Ya no worries, I've been needing to write a blog post and faq entry about it, I'm just trying to hit upon how to write it up really.

Chris

--

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/-/O5xYcxSjNkcJ.

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

[Christopher Forsythe]

It applies to Growl 2, not really Lion on ML.

Which app are you trying this with?

Chris

On Tue, Nov 6, 2012 at 10:18 AM, Randy Hudson <randy....@webfilings.com> wrote:

Chris,

I'm still on Lion.  Changing my framework w/ Detective did not fix my problem.  Does using the Detective to fix this require I'm running under Mountain Lion?

Randy.

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

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

[Randy Hudson]

Skype 6.0.0.2946 (latest).  (So, I rely on clicking on the Growl notification and being sent to the correct conversation in Skype, and that's not working.)

[Charlie S]

Skype 6.0.0.2946 is using 1.2.3 of the Growl Framework, might be able to get Skype/Microsoft (asked on Twitter) 

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

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.

[Christopher Forsythe]

We do, it's in volume licensing, and it is also sandboxed. So it has the same issue with really old frameworks not being able to do the clicking, since sandboxing does not allow for NSDNC in the way that we were using it. So that wouldn't help here.

Chris

On Wed, Nov 14, 2012 at 4:01 AM, DataGreed <cpr.a...@gmail.com> wrote:

same problem here. Why not release an alternate version of growl (not for appstore) that can handle application links from the older version of framework?

воскресенье, 23 сентября 2012 г., 7:21:53 UTC+4 пользователь Sulaiman написал:

--

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/-/SUdFLgqsw0YJ.

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

[Charlie S]

Need to get Microsoft to get Skype to update the GrowlFramework they use

[DataGreed]

I really don't get it. Why can't it handle clicks from older frameworks?

среда, 14 ноября 2012 г., 18:49:41 UTC+4 пользователь Christopher Forsythe написал:

[Rudy Richter]

older frameworks made use of an api called Distributed Notification Center to send the click callback messages to growl.  The reason that this no longer functions is because under the sandboxing model you can send notifications to the distributed notification center but you can't supply any contextual information along with it. That contextual information is what an application would set on a given notification when sending it to growl so that when it got a click notification back it would know which notification was clicked, since its possible to have many in-flight notifications at the same time it needs some context for knowing which one it should present to the user.

What we're looking into fixing after Growl 2.1 ships is that the current model for talking to growl is a single transaction, the application sends growl a message, growl keeps the connection open for a period of time and then closes it if there isn't any user feedback. we ended up timing out the connections because what was happening for certain uses is they would end up with a large number of connections remaining open (large enough that it resulted in Growl hitting the per-application open file limit and resulting in cpu spike the next time the CoreData-backed history database tried to write out its data).  My proposed solution for post-2.1 is that the application's Growl xpc has a local port it listens on for click callback events. this isn't entirely GNTP compatible, but it makes the transactions much simpler, Application sends Growl a message, connection closes, Growl displays the notification. User clicks notification, Growl opens a connection to the App and says "user clicked on notification with this id", the application would then process that request. Neither would have an open connection for long and the max open files, click callbacks, and coredata all would function as intended.

-rudy

[Red Rock Lobster]

Please fix this issue!  I don't want click contexts to time out.

[Christopher Forsythe]

We're working on it. However when Apple breaks something on us that's worked for 10 years and is the basis of how that something works, it's not easy to both fix it and then get it updated in every app that you use. Please be patient.

Chris

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

To unsubscribe from this group and stop receiving emails from it, send an email to growldiscuss...@googlegroups.com.

To post to this group, send email to growld...@googlegroups.com.

Visit this group at http://groups.google.com/group/growldiscuss?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Chris Forsythe

@The_Tick

[Anthony Stal]

Has there been any progress on this issue? I have also purchased Growl and the lack of clicking is pretty frustrating. Thanks

[Christopher Forsythe]

Actually yes. Growl 2.1 and Growl framework 3.0 will have a new change so that it works. The old method should still work fine with 1.2.2.

Apps will need to update to resolve it, which is why it's taking longer to test it out. We like to try to make sure that everything is covered before pushing things public. :)

Chris

Visit this group at http://groups.google.com/group/growldiscuss.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Chris Forsythe

@The_Tick

[Anthony Stal]

Could you help me out? Using growl 2.0.1, and have used GVD to update all frameworks. Still, clicking isnt working (with any of the display styles).

Also, is there any way to get itunes song change notifications without getting the GrowlTunes. Growl used to do that for me til recently.

Thanks!

You received this message because you are subscribed to a topic in the Google Groups "Growl Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/growldiscuss/ycnU7C0Nluo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to growldiscuss...@googlegroups.com.

[Christopher Forsythe]

Growl never did track changes without GrowlTunes or some other application. We'll be submitting a new version of GrowlTunes soon that contains a lot of changes to how it works. :)

Growl 2.1 (not 2.0.1) is the first version to help fix that clicking problem really. It took a while to figure out the right course of action for all parties, typically we try avoid getting devs to update the framework. But we can't do that this time. That'll hopefully be out soon as well.

Chris

[Pedro Perez]

I just noticed this behavior on my setup. It is very much confusing because it just started happening, with no changes. At least I don't think, maybe there was a growl update I didn't notice. Now I don't know if I should try reverting, or something. I found the workaround of manually updated the growl framework of an app. With this solution, it's hit or miss, about 50/50 it'll take me to the app or not. Is this now a well documented issue? with a fix? 

I realize most of my apps have framework 1.2-1.3, but why then did it work perfectly before with growl 2.0? Is all hope lost on growl now that there's Notification Center? I love growl, I want the customization =/. 

On Saturday, September 22, 2012 8:21:53 PM UTC-7, Sulaiman wrote:

[Red Rock Lobster]

On Wednesday, June 19, 2013 11:21:48 PM UTC-4, Christopher Forsythe wrote:

Actually yes. Growl 2.1 and Growl framework 3.0 will have a new change so that it works. The old method should still work fine with 1.2.2.

Apps will need to update to resolve it, which is why it's taking longer to test it out. We like to try to make sure that everything is covered before pushing things public. :)

And what's the status on this now? Thanks.