lewisje / growl

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

Growl 2.0: Action-only configuration still displays Smoke #550

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
The issue is described in two google groups discussions:
https://groups.google.com/forum/?fromgroups=#!topic/growldiscuss/MvjBA9IuPEg
https://groups.google.com/forum/?fromgroups=#!topic/growldiscuss/BMcxXOzHCB8

Versions: OS X 10.8.2, Growl 2.0, Bark 1.1

Tried to achieve native NC notifications for all Growl-enabled apps independent 
of framework version via action-plugin Bark.

Config: visual Growl notifications disabled by default, in "actions" there is 
only Bark enabled, forwarding notifications to OS X disabled, no 
application-specific settings. When Mac falls asleep or after reboot, Growl 
starts showing two notifications - first in NC and second standard themed Growl 
notification (theme Smoke).

To restore expected behavior, I have to go to Growl settings -> Notification, 
click on the style list and explicitly disable visual notifications again (in 
spite of the fact that they seem already disabled). Then everything is alright 
... until next reboot or sleep.

Original issue reported on code.google.com by lex.alt...@gmail.com on 7 Nov 2012 at 6:25

GoogleCodeExporter commented 8 years ago
Flagging as fixed in source, revision [0bcfe7032042] for 2.0.1.  Issue was we 
set the default style to nil, rather than to the empty string, causing it to be 
removed from our preferences plist.  On relaunch (and possibly in other 
situations), we reregister that default as Smoke, which it would precede to not 
find due to that search being based on configuration UUID's not display names 
(during first launch we convert from Smoke to a UUID for a smoke 
configuration).  This would lead to it forcibly choosing a smoke display config 
instead, if smoke was removed, it would simply default to any display config 
available.  If no display configurations were found, it puts out a log message 
every notification.

The work workaround 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 "").

Original comment by dan...@growl.info on 7 Nov 2012 at 7:02

GoogleCodeExporter commented 8 years ago
Wow.. I am out of words, thank you for quick answer! Will try "defaults write" 
as workaround.

Original comment by lex.alt...@gmail.com on 7 Nov 2012 at 7:10

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 11 Jan 2013 at 6:26