"Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> wrote: > Hi, > > I just noticed that the BeOS implemenation of BRoster::FindApp() and > BRoster::Launch() just fail if the preferred application of a given > MIME type is not existing anymore (I replaced the original ShowImage > with our version). > > Wouldn't it be more sensible to search a new default application > instead of just failing? The system provides enough information for > this, anyway; i.e. it could simply remove the preferred app signature > and try again (so that the one from the super type can come into play). > If that also fails, it should have a decent explanation on how to fix > it in the error message. > > Bye, > Axel. Hello I should point out a related thing that can also be considered to be a bug in the R5 implementation. I discovered during coding FileType that GetSupportingApps returns an error in this case: 1. you have an app that handles "image" 2. you have some file type like "image/weird" 3. no application ever handled "image/weird" The very weird part is the "ever" of #3, because if you defined an app to handle that type at one point and then removed it, then it returns B_OK. (and returns apps handling "image") Andrew