cocoaforge

A little bug (I don't think a new Toppic would make sense): In the "About" tab it's still version 1.1.1 (maybe only in the German one, but it is) This is likely because the localizations have not been updated yet and I didn't go through and update that part accordingly. Thank you for the ...

1.1.3 will likely be out before the end of the year.

Marauder911 wrote:Will the 1.1.2 image posted on the main site be updated, or only the repo?

Both. The repository is already up to date, the website takes about 5 minutes to refresh its cache (so yes, it does have an updated image there.)

A new build is up now. Thank you for your report.

A new build is up because display previewing was broken. My apologies to all for having let this slip into the (initial) release build. Please enjoy the improvements we've made.

Bug in the build, I'm fixing right now and uploading.

Folks, 1.1.2 is now available. Download link and version history are on the main page as always.

I doubt this is GrowlMail though, to be honest with you. GrowlMail between .7.6 and 1.1.1 didn't change that much. Oh, it did change a lot. We use a completely different way to listen for incoming messages. Also, GrowlMail is broken on Leopard and makes Mail.app unreliable. It's not sufficient to i...

IngmarStein wrote:

bgannin wrote:A fix for this is targeted for 1.1.3.

Why not 1.1.2? It's just two lines of code...

Because there's actually a schedule for changes and plans for release. I'm not going to drop in changes at random times in the release cycle (late in beta) just because it's easy.

Actually, it's easier to offer 64-bit support than garbage collection. For gc, we would need to ship two different versions, one for 10.5+ and one for previous versions of Mac OS X. As for 64-bit, we can just enable ppc64 and x86_64 for Growl.framework and it should work. Growl-WithInstaller.framew...

Those crashes all seem to indicate Hardware Growler has a memory access problem in a callback from SystemConfiguration (which would be logical given that the crash occurs with Airport) I'll make a note of this for investigation.

A fix for this is targeted for 1.1.3.

I've recompiled the framework myself. Very easy, barely any changes. X86 64 works. I've not tested Carbon or PPC 64 though. I'm glad this worked for you but we'll be taking a graduated approach to releasing upgrades to framework variants due to the scope of change that we are accountable for and ne...

If that's in your logs then HardwareGrowler is behaving correctly. Your system is posting USB messages that HardwareGrowler then displays.

I'm curious as to whether it's actually software (i.e., OS level) or hardware-based. I think you may be right that it's not actually Hardware Growler's fault.

That's a pretty odd crash. While available on 10.4 drain is meant for a garbage-collected app and it went to an obviously erroneous target.

You shouldn't be blitzed with a deluge of notifications like that. Evan was referring to external USB devices.

Actually, most of the system frameworks are 8 way fat binaries because they also include garbage collected and non-GC variants as well. To answer your questions: - No. - Not really, 64 bit is meant for those who need to address large data sets in memory and hit limitations in the 32 bit address spac...

relaxedguy wrote:I removed pref pane from /Library and ~/Library then did a fresh Growl 1.1 install.

It should only be in a single location, not both.

Thank you for the bug report, this will be considered when addressing Leopard compatibility fixes. Currently notifications will appear in the active space you are in, with sticky notifications being stuck in the active space they appear in. (earlier I had stated this wasn't addressable and was incor...