It is indeed fixed for 2.0.1, I thought I had posted that to all the threads on this already, more explanation on the ticket. The work workaround til 2.0.1 is released is to set the display preference to the empty string in our preferences file, either using the file directly and changing the key GrowlDisplayPluginName to an empty entry, or the defaults command (in Terminal: defaults write com.Growl.GrowlHelperApp GrowlDisplayPluginName "").
On Nov 7, 12:27 pm, Alexey Lebedev <[email protected]> wrote: > I sent a bug to Growl team. Maybe you would like to follow its progress > -http://code.google.com/p/growl/issues/detail?id=550 > > > > > > > > On Tuesday, September 25, 2012 3:30:30 PM UTC+4, Kevin Yank wrote: > > > I have Growl 2.0 configured with the Default Style set to ‘No Default > > Display’ and the Default Action set to ‘Bark’. > > > Despite this, applications that are set to use the ‘Global Default’ > > Display Style and the ‘Global Default’ Actions (and for which the specific > > Notification is configured to use ‘Application Default’ for both Display > > Style and Actions) trigger both the ‘Bark’ action and a Smoke display. > > > Is this a known bug? > > > -- > > Kevin Yank > >http://kevinyank.com/ -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
