an0nym0u5 / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Network notified messages are being replaced instead of cascading #630

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Forward message from GfW to Mac Growl with sticky:true
2. Send message A
3. Send message B without clicking(closing) message A

What is the expected output?
Growl displays message A.
Growl displays message B under message A

What do you see instead?
Message B replaces message A.

What version of the product are you using? On what operating system?
Growl 2.1.3
Mac OS X 10.9.3

Please provide any additional information below.
I expect multiple messages are being stayed on the screen even if it came from 
network node.

Original issue reported on code.google.com by changjoo...@gmail.com on 29 May 2014 at 10:49

GoogleCodeExporter commented 8 years ago
are the messages being forwarded from GfW all using the same notification 
identifier? if they are then that might explain the behavior you're seeing. If 
a message is set as sticky and a new notification is received with the same 
notification identifier associated with it, the sticky notification gets 
replaced by the incoming one.

Original comment by r...@growl.info on 29 May 2014 at 10:02

GoogleCodeExporter commented 8 years ago
Hi,
Thank you for your feedback.

1. Changing of notification-id does not affect this symptom with 
/id:abc123_{random} switch.
2. FYI, Changing or Making same coalescing-id did not affect this symptom 
either with /c:{random} switch.

No matter what I do with {{notification-id}} or {{coalescing-id}}, it always 
replaces previous message.

Original comment by changjoo...@gmail.com on 30 May 2014 at 1:12