Version: 2.0 (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages Well the title is pretty self-explanatory. I think it is useless to have the OSD pop up when selecting a song or playing a playlist if the user has the amarok window open. It just gets in the way, showing information that is already shown in amarok itself.
It could be difficult to detect if Amarok is actually visible or not, if you take cross platform into account. It could be visible, but on a different virtual desktop (Linux), it could be visible, but hidden by another application on top of it, etc. This isn't as easy to get right as it may seem. Then there is is the question whether this should become an option or the standard behaviour. Retargetting to 2.1.
It can be argued (and i think it probably should) that since an OSD provides information to the user when they are otherwise engaged, the OSD should *not* be forced on them when they in fact *are* engaged in Amarok already. So yes, i for one would agree with this request :)
I agree with your idea, had just the same thought when I installed amarok2 today. But I would ask for a slightly different feature: I think it would be great to add an option in the OSD dialogue, to only show the OSD, when amarok2 is closed and only shown in the tasks. That way it would be only shown when amarok is really not visible at all. Downside would be of course, that you won't see the OSD when you haven't really closed amarok2, but if you have some panel open, you will see some information about the current song there. So I think if this is really optional, it wouldn't hurt. Default could also be turned off.
An additional thought. Is it possible for Amarok to use the notifier when a song changes? Just a thought.
Kopete already has different notification schemes: one for active chat window, another - for inactive ones. Why not use that code?