Bug: Growl does not respect notification-specific display style settings

[GoogleCodeExporter]

What steps will reproduce the problem?
Two experiments:

EXPERIMENT ONE
1. Set a default display style (for example, 'Plain')
2. Set an application to use a different display style (for example, 'Smoke') 
via Applications > (app name) > Application Settings > Application's Display 
Style
3. Test Growl in the above application — it should display using Smoke

EXPERIMENT TWO:
1. Repeat the above
2. Set a notification-specific display style (for example, 'Music Video') via 
Applications > (app name) > Notifications > Display Style
3. Test Growl in the above application (for that particular notification type) 
— it should continue to display using Smoke, NOT Music Video

What is the expected output?
The 'Display Style' setting on an application's Notifications tab should 
override the setting on the Application Settings tab.

What do you see instead?
The 'Display Style' setting has no effect, and all notification types continue 
to use whatever display style is set for the entire application.

What version of the product are you using? On what operating system?
Growl 1.3.1
OS X 10.7.2
iMac7,1

Please provide any additional information below.
This problem negatively affects Prowl integration in particular, which is why i 
noticed it. For instance, i want Growl notifications for highlights and private 
messages in the IRC client Linkinus to get forwarded to Prowl, but ONLY those 
types of notifications — not CTCP requests or invites or anything else. So i 
set Linkinus as a whole to use, say, Smoke, and then i set the 'New Highlight' 
and 'New Private Message' notifications to use Prowl.

I expected this of course to make it so that Growl would only forward 
highlights and private messages. Instead, it had the effect of disabling Prowl 
for that application completely.

PS: I have tested this with many different combinations of display styles, so 
it is not just a Prowl issue.

Cheers

Original issue reported on code.google.com by dana.my....@gmail.com on 28 Nov 2011 at 2:47

[GoogleCodeExporter]

Hello, I would like to know if you are still seeing this as of 1.3.3, as I 
cannot reproduce this anymore.  

Original comment by dan...@growl.info on 1 Feb 2012 at 4:15

• Changed state: WaitingOnUser
• Added labels: Product-Growl

[GoogleCodeExporter]

Setting to 1.4.1. If we get no response by time 1.4.1 is close to being 
completed, close the ticket.

Original comment by ch...@growl.info on 8 Feb 2012 at 3:23

• Added labels: Milestone-1.4.1

[GoogleCodeExporter]

Hi there! Sorry for the delay in responding. I've just tested it now in 1.3.3, 
using the following configuration:

1. Global default style (as set on the Displays tab) is 'Prowl', with a Prowl 
display style of 'Mono'

2. Default style for Linkinus (as set on the Applications tab > Linkinus > 
Application Settings) is 'Plain'

3. Display style for CTCP Request (as set on Applications > Linkinus > 
Notifications) is 'Default' — my expectation therefore is that CTCP requests 
should generate a notification using the Plain style, since this is the default 
for this application

4. Display style for New Highlight is 'Prowl' — my expectation therefore is 
that highlights should generate a visual notification using Mono, and 
additionally forward the notification to my phone using Prowl

Actual results:

Both CTCP requests and new highlights generate a notification in the 'Plain' 
style. Prowl does not forward to my phone.

However — i may have an answer for why you can't reproduce this.

I've tried reproducing the problem in Transmission using a similar set-up. This 
time it worked as expected... so obviously the problem varies somewhat.

I recently got a new Macbook Air, and so i had to set up both Linkinus and 
Growl anew on that machine. What i've noticed on that machine is that Linkinus 
REFUSES to register with Growl. The reason it registered OK on my iMac seems to 
be that i had the old Growl installed on it previously, and that carried over. 
A friend had a similar experience and confirmed that this was the only way he 
could get Linkinus to register with Growl.

So my theory is that Linkinus was not updated properly for the new version of 
Growl, and somehow that causes the notification style settings to not work 
properly.

Original comment by dana.my....@gmail.com on 8 Feb 2012 at 11:26

[GoogleCodeExporter]

Nope, you explained exactly why Chris couldn't reproduce it. Linkinus was used 
as the basis for the test.

its Growl implementation has been broken for years. ultimately it registers 
several different types of notifications that it might send to Growl but 
instead sends them all as the same notification type.  It has frustrated me for 
quite awhile now.

I'm pretty sure most/all the notifications that Linkinus sends come through as 
"Event Alert" notification type.

if you can confirm I will close this ticket since its actually a problem with 
Linkinus.

Original comment by rarich...@gmail.com on 24 Feb 2012 at 4:57

[GoogleCodeExporter]

I'm going to close this since Rudy determined what's going on and we've had no 
feedback since February.

Original comment by ch...@growl.info on 21 Jun 2012 at 3:17

• Changed state: Done