cocoaforge

Since they've never heard of Growl, I highly doubt they are informed enough to pinpoint it as the sole cause. Growl doesn't directly interact with hardware (or control the cursor) so it's a dubious claim. To uninstall Growl you need to stop Growl (you can use the button in the pref pane or the item ...

excomax wrote:There are several other threads and posts about this problem. And there's still no solution or update from Logitech itself.

However, 1.1.3 will address this from our end.

1.1.3 is currently in late beta. It has not yet been publicly released.

I'd just wait for 1.1.3 as it's in the pipeline for release.

We've addressed it in the next update, as the beta release notes indicates. Applications will need to update their included Growl framework for it to entirely go away.

darkxsun wrote:Looks really great. My only suggestion is this:

Previously there was some text telling what version of Growl was current, and its release date. If this is still there, I'm missing it. I thought that was very useful.

-Bill.

Fixed, thank you for your report.

(stickied at the top of this forum)

http://forums.cocoaforge.com/viewtopic.php?f=6&t=15349

If Growl is working it's not actually a problem with Growl then (it displays whatever is sent to it) so you should look to help from those who are familiar with GyazMail, which seemingly no one is here.

Simple answer - it's not Growl. When Growl's not installed iScrobbler is using its own notification display mechanism.

Installer on 10.4 only allows installing to a defined location, on 10.5 you can choose your own install location (such as in ~) We have removal instructions on the website.

Have you reviewed Adium's instructions to check your settings in it?

Only a few threads down when I just looked...

http://forums.cocoaforge.com/viewtopic.php?f=6&t=16891

1.1.3 isn't publicly distributed, it's currently in beta, and others have found it on our beta page. Yes, it fixes GrowlMail/Leopard.

You could write your own shell script and use the growlnotify command line utility to post a notification as you determine.

I'm not familiar with Perl but it's binding component is available in the 1.1.2 SDK download, which I just verified.

Uninstalling and reinstalling won't change anything, you need to understand what your configuration is and why things occur as they do. Each display can have it's own durations as I noted previously, and each application can have its own associated display (so Adium could have Smoke, while GrowlTune...

Ah, this is the display duration that can be found under the Displays tab. You can change the duration per style (there is not one overriding setting) from this location.

Relaunching Skype will likely re-add it to the list as applications re-register and aren't suppressed (to my knowledge), which was a recent thread topic.

As noted in step 3, you need the developers' download for your corresponding version of Growl. You'll then find it in the Perl bindings section.

That's an oxymoron :) A sticky notification (no need for caps shouting) stays on screen unless the user specifically interacts with it to remove it. There's no timeout associated with sticky notifications. The only option that would emulate this is to leave notifications on screen if you are idle, w...