sigonasr2/jmonkeyengine
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed a exception in Materal toString with blender materials.

Browse Source 
Some blender materials have null Material Param keys. This shouldn't
throw an exception in a toString method. So rather than throwing a
OperaitonNotSupported exception a string is returned informative of the
null state of the key.
This commit is contained in:
delt0r 2017-02-08 14:53:45 +13:00
parent 8dcc67a318
commit f416d7af18
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
jme3-core/src/main/java/com/jme3/material/MatParam.java
View File

@ -237,7 +237,11 @@ When arrays can be inserted in J3M files
Texture texVal = (Texture) value; Texture texVal = (Texture) value;
TextureKey texKey = (TextureKey) texVal.getKey(); TextureKey texKey = (TextureKey) texVal.getKey();
if (texKey == null){ if (texKey == null){
throw new UnsupportedOperationException("The specified MatParam cannot be represented in J3M"); //throw new UnsupportedOperationException("The specified MatParam cannot be represented in J3M");
// this is used in toString and the above line causes blender materials to throw this exception.
// toStrings should be very robust IMO as even debuggers often invoke toString and logging code
// often does as well, even implicitly.
return texVal+":returned null key";
} }
String ret = ""; String ret = "";