Open GoogleCodeExporter opened 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
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
Original issue reported on code.google.com by
changjoo...@gmail.com
on 29 May 2014 at 10:49