Closed GoogleCodeExporter closed 8 years ago
Why would you need to show/hide mist options, since it's simply a on/off?
Wouldn't that also apply to Growl as well? This seems like complication to a
simple process, which is why I'm asking.
Original comment by ch...@growl.info
on 22 Dec 2011 at 5:03
If the user has Growl running, I want to hide the option to enable/disable Mist
(since they can configure notifications in Growl.app).
Original comment by livings...@gmail.com
on 22 Dec 2011 at 5:08
I get that is what you want to do, but why would you do that instead of have a
"enable notifications" that the user selects that handles either Mist or Growl,
regardless of which one it is?
Original comment by ch...@growl.info
on 22 Dec 2011 at 5:25
I think it makes sense to enable and configure in the Growl prefs. Regardless,
this would still be needed for showing/hiding a button to open Growl, relevant
text, etc.
Original comment by livings...@gmail.com
on 22 Dec 2011 at 5:33
Alright, I think i get it now. Let me summarize this and confirm that this is
what you mean.
1) You want to have some preference to enable/disable notifications in general.
2) If Growl is running, you want to present the user with a button to configure
your application in Growl via the new URL scheme in 1.4.
3) If Growl is not running, you would likely not show a button at all to
configure notifications in Growl.
Does this summarize what you want?
Original comment by ch...@growl.info
on 22 Dec 2011 at 5:40
Yes. except for three I have a simple checkbox to enable or disable Mist
notifications. I already have this working, and can determine which set of
options to show based on the framework's isRunning method, but I have no way to
know if they app is launched or quit to change which set of options are shown
while running.
Original comment by livings...@gmail.com
on 22 Dec 2011 at 5:56
Original comment by ch...@growl.info
on 31 Dec 2011 at 3:47
Original comment by ch...@growl.info
on 27 Aug 2012 at 1:55
Closing as fixed in source, for Framework 3.0. The new isGrowlRunning property
on the proper singleton is observable, and can be used as a readonly binding.
Original comment by dan...@growl.info
on 18 Jun 2013 at 10:11
Original issue reported on code.google.com by
livings...@gmail.com
on 22 Dec 2011 at 1:48