HydrogenAudio

for user of Biography View notice that the component should be removed:

The following components are obsolete in this foobar2000 version:
 - foo_uie_biography.dll : Biography View
These components no longer provide any new functionality and should be removed.

[edit]

• Bug: possible unnecessary tag reloads on Media Library contents on startup.

I don't know what exactly was changed but start-up time is at least twice faster than before

Um... how on earth was that decision reached? I mean I could understand if it was blocked because it's buggy or something, but obsolete? No new functionality? That doesn't sound right...

for user of Biography View notice that the component should be removed:

Code: [Select]

The following components are obsolete in this foobar2000 version:
 - foo_uie_biography.dll : Biography View
These components no longer provide any new functionality and should be removed.

I dont get it. How can you get biography view features without the plugin?
Do you mean tags are now updated with all those lastfm infos? Can album and artist images be cached?

Quote from: 2E7AH on 2009-11-27 17:51:05

for user of Biography View notice that the component should be removed:

Code: [Select]

The following components are obsolete in this foobar2000 version:
 - foo_uie_biography.dll : Biography View
These components no longer provide any new functionality and should be removed.

I dont get it. How can you get biography view features without the plugin?
Do you mean tags are now updated with all those lastfm infos? Can album and artist images be cached?

Same question here

foo_uie_biography attempts to provide its own cover art data for arbitrary file formats, just like foo_covers does. This triggers the startup checks and gets the component mis-identified as foo_covers. This component still works as intended; the error message will be corrected in the next version
This is what happens when your component misuses the APIs; even the foo_uie_biography author is aware that his code is problematic according to the readme (mentions conflicts with foo_covers).

foo_uie_biography attempts to provide its own cover art data for arbitrary file formats, just like foo_covers does. This triggers the startup checks and gets the component mis-identified as foo_covers. This component still works as intended; the error message will be corrected in the next version
This is what happens when your component misuses the APIs; even the foo_uie_biography author is aware that his code is problematic according to the readme (mentions conflicts with foo_covers).

Ok that s one thing, but saying the plugin doesnt provide anything useful anymore is really wrong!

Geez!
It triggers a stock - canned - pre typed response from the installer. Foobar really did not mean anything personal.

terry

nobody is saying that, only the component places itself there by it's own mistake

[edit] doh, terry

Thanks for clearing that up Peter.