cocoaforge

I don't think this would be related to your platform, but Leopard is not an officially supported system as it is currently pre-release. If it is specific, please check back when it can be discussed without an NDA.

I don't think anyone in this thread has handled themselves appropriately. Let's drop this situation and go back to enjoying a seamless notification system and not a soap opera.

Chris, please lock this thread.

Or you could unique names for each group and use the tear off groups from the SoC project in 1.2 when it is released to keep them separate.

Thanks for finding the leak and even more for determining how to fix it! I've followed your advice and made + (NSDictionary *) registrationDictionaryByFillingInDictionary:(NSDictionary *)regDict restrictToKeys:(NSSet *)keys return an autoreleased dictionary instead of a retained one as it was doing...

iMacBook wrote:Gah. I can't wait forever!

Nor shall you. It will be released at some point, that point just hasn't been determined/announced/etc.

Nib wrote:I have also tried to use the WOCachingEnabled NO by writing this to the terminal:
Code: Select all
defaults write com.Growl.GrowlHelperApp.plist WOCachingEnabled NO
But without any luck.

This wouldn't have any effect, GrowlHelperApp isn't a WebObjects application, nor does it use WebObjects.

You talk in two different tenses here, please clarify. Has Growl's Bezel display ever supported the specific behavior (pop onscreen, fade out) or not? If not, it's not a regression and you don't 'go about getting it back' because it's never been there. Mac OS X's onscreen notifications are entirely ...

Crypt wrote:I'm surprised this was also never done for GrowlTunes as well

GrowlTunes Plugin (GTP), the successor to GrowlTunes, will be invisible since it's a plugin for iTunes and only appears in there.

I don't think so, but I'm not making any promises either

There's no reason we can't wrap an interface around the hack to make this activity simpler.

Non-Webkit: Smoke, MusicVideo, Bubbles, Nano, iCal

"rk wrote: Growl 1.1 looks great, but I have one question: Where's the GUI option to enable and disable logging of Growl notifications? This was removed in 1.1 from the pref pane. That was more a developer feature than a user feature. Redone logging is certainly possible in a future release (I...

The_Tick wrote:We're hoping to put out growltunes plugin with 1.2, which will allow for optional field selections.

This issue is filed and being tracked with http://trac.growl.info/ticket/727 and will be addressed in 1.1.2.

Ditto. And, please, add 'Custom...' menu item at the bottom that will allow to pick sound from any other location. Thanks! We will be adding support for reading from the standard locations, but not for a Custom... sound at this time. It's preferable to follow the patterns inherent within the OS, fo...

We should move the Java bindings over to this to be forward-compatible.

What's your registration dictionary code look like?

You're hidden command line option would be to use growlnotify to post notifications, but it's not actually recommended to use if bindings are available. That said, I'm not terribly familiar with the Java bindings to give an informed answer

It's not actually an issue, it's an opt-in feature of Growl for developers. When a lot of notifications are sent you can use "coalescing" to provide the effect you see, in which a single Growl notification is re-used to display all the queued up messages. To change this behavior you'd need...

What would more accurately convey "Growl" and/or visual notifications? I think the current paw is quite workable myself.

cocoaforge

Search found 1817 matches

Re: "Enable logging"