I have added an entry to our forthcoming FAQ about this:
http://growl.info/documentation/faq.php
(I haven't yet published a link to that page from the rest of the
website, so don't be embarrassed that you didn't see it.)
Please let us know if that answer is unclear, or if you continue to
have this problem.
Try what the new FAQ says:
http://growl.info/documentation/faq.php
And please let us know whether that helps you.
If not (and this goes for cuiweicui, too), please do the following:
1. Take a screenshot of the Trash window, showing the files.
2. Select some (or all) of the recovered files.
3. Right-click on any file in the selection and choose “Create Archive
of X Items” or “Compress X Items” (where X = some number).
4. Upload the zip file and the screenshot to our Files area:
Interesting. Is it only the one, every time?
Judie, what about you? We're still waiting for your screenshot and zip
of the growlRegDict file(s).
There wouldn't be. Growl is a preference pane (pane in the System
Preferences application), not a preferences file (file of your
preferences).
> I have a PreferencePanes folder in the Library folder of my HD
> (Macintosh HD).
>
> I am not sure how to view the Root Level of my HD.
You already found it. The “Library folder of [your] HD” is at the
root level.
> Would a Growl prefpane in the Library Folder of a Previous Systems
> folder be causing a problem like this?
Unlikely. You can delete it if you want, anyway. The Previous Systems
folder only exists so that you can recover stuff you previously had
installed; since you've already reinstalled/upgraded Growl on your
current system, you no longer need to keep the previous system's copy.
> When I log onto my username, it looks as though something tries to
> launch and crashes, from the way my dock behaves.
That's not Growl. You don't see Growl launch at all.
In the Accounts pane in System Preferences, look at your login items.
It's probably one of those (but not Growl).
> When I look in my Recent Items in the Apple dropdown menu, my
> documents list is filled with .growlRegDict files.
Interesting. The Growl framework opens them in such a way that they
don't show up in Recent Items. Some application that you're using is
using a very old version of the framework—one that wasn't so smart.
I'll write an application to inventory your applications, filter the
list down to those with a Growl framework, and list them all with app
and framework version. Stand by. ☺
Yup. Like I said, it's the Growl framework that creates and opens
those files. The Growl framework is how applications talk to Growl.
Every application that uses Growl has a Growl framework somewhere
inside the application (with the exception of Safari and Mail, where
the framework is in GrowlSafari/GrowlMail).
> … but I only seem to get files in the trash when I use Adium, not
> when I use other apps (like Safari) that use Growl notifications.
What version of Adium?
> I did an experiment of IMing between two of my screen names and
> rebooted and got one recovered file in the trash, so I am uploading
> it and a screenshot of the trash with the flie in it to the group
> files, also, as previously requested.
Your .growlRegDict file is from Growl itself. That, coupled with the
fact that:
> … I did put the Growl.prefpane from my previous system in the trash
> before I rebooted. And there were no .growlRegDict files in my
> Recent Items when I rebooted this time.
suggests that that old Growl was what was leaving behind
your .growlRegDicts.
I'm still curious about your version of Adium, though.
Well, you don't need it anymore, but I went ahead and finished it
anyway. Here it is:
http://growl.info/files/Growl_Version_Detective-1.0b1.zip
This is a troubleshooting utility that will tell you:
1. What version of Growl you're using.
2. The name of every app on your system that uses Growl, along with
each app's own version and the version of the Growl framework that
it's using.
The first thing to check is whether you have the latest version of
Growl. Go to the Growl website and compare that version number to the
one at the top of the GVD window.
The second thing to check, if you're having a problem with a specific
app, is whether that app is using an old version of the framework.
This is easy to tell, because we keep framework versions synchronized
to Growl versions. Each app has its own copy of the framework, so it's
possible (and, currently, disturbingly likely) for your apps to have
different versions of it.
If, in fact, the framework in the problem app is out-of-date, then
your next step is to check for a newer version of the app. If there
isn't one, then you may want to send a polite note to the app's
developers, to inform them that the framework they're shipping is out
of date.
Well, you don't need it anymore, but I went ahead and finished it
anyway. Here it is:
http://growl.info/files/Growl_Version_Detective-1.0b1.zip
This is a troubleshooting utility that will tell you:
1. What version of Growl you're using.
2. The name of every app on your system that uses Growl, along with
each app's own version and the version of the Growl framework that
it's using.
It's not really a developer tool. The only thing I could see an app
developer using this for is checking what version of the framework
he's using in his own app—and there are easier ways for the developer
to determine that. As such, it doesn't belong in the SDK.
This is a troubleshooting tool *for users*. So, we should either
distribute it separately or bundle it on the Growl disk image.
>
> On Jun 01, 2008, at 13:54:51, Chris Forsythe wrote:
>> I think it'd be useful to ship this with the SDK at some point,
>> after it's been vetted further.
>
> It's not really a developer tool. The only thing I could see an app
> developer using this for is checking what version of the framework
> he's using in his own app--and there are easier ways for the developer
> to determine that. As such, it doesn't belong in the SDK.
>
Good point.
> This is a troubleshooting tool *for users*. So, we should either
> distribute it separately or bundle it on the Growl disk image.
Hrmm.. that's not a bad idea. A troubleshooting dmg would be pretty
awesome I think. A button to enable logging/disable logging
(beephammer code could be swiped for that), this tool, and a few
others everyone has been coming up could be put into a more refined
bundle. I think it would be awesome.
Maybe even something that puts log files into a user submittable
archive (zip, tbz, whatever) would be sweet.
Chris