cocoaforge

… Maybe we should add a link within the uninstaller … There's no “within the uninstaller”. It's an AppleScript. And when we rewrite the uninstaller in pure Cocoa, we shouldn't add the link there either. We should make it just work. I agree (about just fixing it), and I was referring to the rewrite ...

Until this issue with Growl, I didn't know (nor any need to know) that additional preference panes that appear in the System Preferences were stored in /Library/PreferencePanes. FYI, another way to delete prefpanes is in System Preferences itself. If you right-click on a third-party prefpane, it pr...

Folks,

I'd like some help. This month I am going to focus on just the documentation for Growl. However, I'd like to get some help with where the problems are, and suggestions to fix problems with it.

Sounds like something we need spam filtering for

Side note, what did you want Growlmail to do that it did not do?


Go into /Library/Mail/Bundles and ~/Library/Mail/Bundles and look to see where GrowlMail is at. Quit Mail, remove GrowlMail, and you are done. That's the standard, OS X way to remove a mail bundle.

jowie wrote:

darmok wrote:Is it more yet?

There doesn't seem to be much development/traffic with Growl

We're down from the 15-30 devs we used to have, to about maybe 5 total, if that. The codebase is rather big for that amount of people, who are all pretty busy.

I don't get how the fade can be that annoying, I'll have to play with it more. Is it more yet? Have you had a chance to gander at the development mailing list lately? We typically don't discuss development on the forums: http://groups.google.com/group/growl-development/browse_thread/thread/bb197180...

That would be the only way to do that, yes.

It won't show up as a clickable link. However, if your php bindings support them, growl supports something called a clickback. Basically if they click the notification, it'll go back to the application and say "they clicked it" from which you can do whatever you want with that knowledge.

Are you trying to remove Growlmail or Growl? I ask because you mention using the uninstaller and it has a known issue with growlhelperapp. That uninstaller is for Growl, not GrowlMail.

I think your thread subject could have had some kind of information in it. Other than the fact that I can see you have a perceived bug, I don't know what else you're wanting to yell about. Honestly, if it's been happening for every single version, have you been filing dev tickets or reporting it for...

hermeneut wrote:Thanks for that The_Tick. Unfortunately, I don't have time to install this and then backtrack to QT 7.4.4. A simple yes or no would be of considerable assistance!

Why do you think we'd have the time to do it if you do not have the time to do it? I find that odd.

Try it in 1.1.1

hermeneut wrote:Does Perian 1.1.1 fix this issue?

Try it and find out.

We're going to work on fixing the font sizes on big monitors, screenshots/pictures help us there the most, along with screen dimensions and sizes.

No, and that's what programs like logrotate do.

Great work Dimmuxx

Mind if we lock this thread? I think we've reached a happy conclusion here.

You can enable logging with BeepHammer, which I think is in the sdk.

Not right now, but that's something we've discussed doing for later.

chiefsfan46 wrote:with the growl 1.1.4 and mac X 10.5.5 i cant go to the growl web page or donate page without getting a authorization warning, plus when i check for updates, system preferences crashes

Growl cannot cause this.