Growl 1.3 and SABnzbd+: notifications not working

[Horse Calledhorse]

Upgraded successfully from 1.22 and wanted to let you know that SABnzbd+ 0.6.9 should be added to the list of apps that don't work correctly. It's recognised under the Growl apps "Applications" tab but none of the notifications are displayed. I've contacted one of the developers to let them know, and apparently they're already using the 1.22 framework, so it must be something else causing it not to work.

[Christopher Forsythe]

Ask them to contact us on the development list:

http://groups.google.com/group/growl-development

Chris

On Tue, Oct 4, 2011 at 6:38 PM, Horse Calledhorse <equus...@gmail.com> wrote:

Upgraded successfully from 1.22 and wanted to let you know that SABnzbd+ 0.6.9 should be added to the list of apps that don't work correctly. It's recognised under the Growl apps "Applications" tab but none of the notifications are displayed. I've contacted one of the developers to let them know, and apparently they're already using the 1.22 framework, so it must be something else causing it not to work.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
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.

[HorseCalledHorse]

It's not a huge priority for them, which is understandable, and as far
as they can tell their code is doing everything properly.
The good news is they're working on a new implementation based on the
GNTP protocol for the next version of the app, which should work well
with 1.3. In the meantime I might have to downgrade to 1.22.

On Oct 5, 11:00 am, Christopher Forsythe <ch...@growl.info> wrote:
> Ask them to contact us on the development list:
>
> http://groups.google.com/group/growl-development
>
> Chris
>

[Peter Hosey]

On Oct 4, 2011, at 16:38:44, Horse Calledhorse wrote:
> I've contacted one of the developers to let them know, and apparently they're already using the 1.22 framework, so it must be something else causing it not to work.

They may be conditionally talking to Growl only if isGrowlInstalled returns YES. 1.2.x frameworks don't know Growl is an application; they look for a prefpane, which they don't find, so they can't see that it's installed (but they can see that it is running, which is how notifying works).

Applications should not talk to Growl conditionally; they should do it unconditionally. The framework will harmlessly drop the message if it can't deliver it to Growl because Growl is not installed or is turned off.