On Aug 30, 2009, at 05:35:09, CJ Yetman wrote:
> I have 10.5.8 and Growl 1.1.6. I will probably upgrade to Snow
> Leopard soon.
Either way, you'll be able to use Growl 1.2.x.
> I don't know how to reliably replicate the problem, but I can try to
> figure it out if it would be useful.
We've figured out the origin of Growl-[UUID].growlRegDict files
earlier in this thread.
> I believe they only show up after having run a specific application
> that sends notifications through Growl.
The Growl-[UUID].growlRegDict files come from Growl itself. Growl
doesn't delete them if it's turned off (which is a bug).
> The filenames don't seem to have any hints as to which app
> created them, …
They do. The filename of .growlRegDict files created by the Growl
framework is always:
[Originating application]-[UUID].growlRegDict
That's how we know the Growl-[UUID].growlRegDict files come from Growl
itself: The filename says so.
> … but almost every time I opened one up and looked at the text, I
> saw something that made me think it was related to Speed Download.
> Speed Download just recently released an update and the release
> notes mentioned that they had updated the Growl Framework, which I
> thought would finally solve the issue, but I have gotten the
> recovered files in the trash since then.
You're right. I can reproduce this.
There are a couple of things different from what we do, though:
1. The Growl framework puts the files it creates into
NSTemporaryDirectory(). On my (Leopard) system, this returns a
pathname ending in “-Tmp-”. Speed Download puts its .growlRegDict in a
sibling directory to -Tmp- named “TemporaryItems”.
2. The Growl framework puts the application name and process ID number
into the filename. This is unconditional, and even if we abbreviate
the filename for length reasons, we'll cut off the UUID first. The
name of the file Speed Download creates is [UUID].growlRegDict—both
the application name and process ID are missing.
Thus it appears that Speed Download itself, not the Growl framework,
is creating this file. You should report this bug to them.
> If memory serves... I believe I've also found some recovered Growl
> files that referenced or hinted at Firefox as well, but I'm not
> positive... it's been a long time since I saw one of those.
Maybe, but they don't use the Growl framework. I don't know whether
they're currently just using the Growl framework source without a
framework, or whether they're talking to Growl using their own
original code.
> There have been previous threads about this in the past.... once there
> was discussion about the change of Growl from being installed system
> wide or per user and deleting the duplicate/older version, …
Yeah, that problem is where you have an older Growl installed (some
really old versions did have major problems of not
deleting .growlRegDict files) and the application targets that one
instead of the newer one. It's practically died out now, as
practically everybody who had it has either already upgraded, moved to
another machine, or abandoned Growl.
> … then there was a thread where someone eventually posted a little
> app that showed the Growl Framework version of every app on your
> computer that had the Growl Framework....
The theory there being that an app may be using an ancient version of
the Growl framework.
> I used that and found that Speed Download and Firefox have/had a
> woefully out-of-date framework version, …
Actually, Firefox doesn't use the Growl framework, and it accordingly
does not show up in Growl Version Detective (and I have three
different versions of Firefox installed). It's weird that it would
show up for you.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en
-~----------~----~----~----~------~----~------~--~---
