> "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote: > > Rene Gollent <anevilyak@xxxxxxxxx> wrote: > ... > > > We can't know if we can/can't handle a file > > > without first reading its container headers > > > to find out the codecs used within it. > > > Only then can we check if we have the necessary > > > codecs or not. The problem being talked about > > > here is rejecting them based off the BEOS:TYPE > > > attribute without even looking at the file data > > > at all, which is almost certainly not correct. > > > > We could at least limit the allowed supertypes to > > application, video, and audio, I would guess. > > I´m not opposed to having audio/* and video/* > in MediaPlayer´s supported types list, but maybe > something like this is possible: > > If MediaPlayer is able to enumerate the addons > available to it and if it is able to reasonably well > translate that addon information to supported file > types, then it would be possible for MediaPlayer to > update its own Supported Types settings, and thus > better communicate which file types it supports and > filter out the rest, which are likely not supported. B_DONT_DO_THAT! This will not work in a multiuser setup, apps will no longer be allowed to touch themselves! François.