1. 19 8月, 2012 1 次提交
  2. 22 7月, 2012 1 次提交
    • D
      Improves/extends whitespace parsing in OBJLoader · d7b9dfd3
      Dahie 提交于
      I had the issue that some of my OBJ-files weren't loaded by the OBJLoader provided in the examples. Parsing the file crashed with this exception:
      
      Uncaught TypeError: Cannot read property 'x' of undefined Three.js:13
      THREE.Vector3.addSelf (Three.js:13)
      THREE.Geometry.computeCentroids (Three.js:91)
      THREE.OBJLoader.parse (OBJLoader.js:295)
      xhr.onreadystatechange (OBJLoader.js:21)
      
      I traced the error to the OBJLoader and my OBJ files. The obj files were exported by 3ds Max Wavefront OBJ Exporter and slightly differ in format:
      
      Where the loader expected:
      v 0.4500 1.5256 0.6595
      
      they were:
      v  0.4500 1.5256 0.6595
      
      Note the extra space. This threw off the regular expressions, the vertices weren't parsed and the computeCentroid failed. This commit changes the regular impression to accomodate this variance.
      d7b9dfd3
  3. 05 7月, 2012 1 次提交
  4. 26 5月, 2012 1 次提交
  5. 25 5月, 2012 1 次提交
  6. 08 5月, 2012 1 次提交
  7. 07 5月, 2012 2 次提交
    • M
      Using event.content for consistency. · 9c9cf2f2
      Mr.doob 提交于
      9c9cf2f2
    • M
      OBJLoader now using EventDispatcher. · ede49a82
      Mr.doob 提交于
      The only confusing part of this approach is the event object that gets dispatched. For ImageLoader you need to look for event.image, and for OBJLoader you need to look for event.object. Maybe it should be consistent for all and just be event.content?
      ede49a82
  8. 22 4月, 2012 1 次提交
  9. 21 4月, 2012 1 次提交
  10. 18 4月, 2012 6 次提交
  11. 17 4月, 2012 8 次提交