Suggestion: wildcard surface texture types in catalogs and Meshes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. specify a surface texture image type of * either in a catalog or in a Mesh 
material definition
2. load the catalog
3. observe no surface texture image being applied to the object

What is the expected output? 
a colorful object
What do you see instead?
the object's default materials

What version of the product are you using?
r231
 On what operating system?
win7 pro sp1 x64

Please provide any additional information below.

It'd be nice, for example, to be able to replace a jpg surface texture by a dds 
texture without having to edit a catlog or regenerate a model. 

Also, some modeling packages can't use some of surface texture file types that 
Cosmographia supports. It'd be nice not to have to edit their mesh outputs to 
specify the appropriate file type.
(Anim8or can't handle png or dds textures. The only filetype supported by both 
programs is jpg.)

Original issue reported on code.google.com by s...@cornell.edu on 30 Apr 2011 at 7:56

[GoogleCodeExporter]

Original comment by clau...@gmail.com on 1 May 2011 at 11:38

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Closing this. The convenience of wildcard extensions doesn't outweigh the extra 
complexity introduced.

Original comment by clau...@gmail.com on 27 Jan 2015 at 7:38

[GoogleCodeExporter]

Original comment by clau...@gmail.com on 27 Jan 2015 at 7:39

• Changed state: WontFix