Hi Robert, On 15/12/09 11:33 AM, Robert Osfield wrote: > On Tue, Dec 15, 2009 at 9:43 AM, Ulrich Hertlein <[email protected]> > wrote: >> On 15/12/09 10:29 AM, Ulrich Hertlein wrote: >>> As I understand it 'addFileExtensionAlias' really only works with plugins >>> that don't check >>> the extension name. >> >> I should add: ... or that have the extension in their supportsExtension list. > > No this isn't a correct understanding. The file extension alias for > for plugins that handle a wider range of file extensions that just the > extension component of the name of the plugin, or for where the file > extension doesn't match the name of the plugin, the quicktime time is > a case in point.
Hm, I'm afraid I don't quite understand. Isn't the following the case? - plugin X will automatically be associated with extension 'X'. - to support more extensions the plugin must say that it supports 'Y' *and* the Registry must map extension 'Y' to 'X', because otherwise plugin 'X' won't be considered/loaded for extension 'Y'. (I'm not trying to argue what should be done to have an application tell a plugin to handle another extension, or if that's even a case that needs to be supported.) Cheers, /ulrich PS: The Qt plugin might be a bad example because in addition to supportsExtension() in the ctor it explicitly checks the extensions in accepts*Extension(), so to support a new extension one would need to add this in three places. PPS: And it *also* calls addFileExtensionAlias() from the ctor. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
