Skip to content
Snippets Groups Projects
  1. Aug 19, 2011
    • Andrew Hale's avatar
      Version 0.1.1: · 2bc0a0df
      Andrew Hale authored
      - Fixed an issue where 'Add New Ivy' and 'Add New Default Ivy' did nothing
      - Updated Blender version to 2.59
      - Updated Blender revision to 39307
      2bc0a0df
  2. Aug 18, 2011
  3. Aug 16, 2011
  4. Aug 15, 2011
  5. Aug 12, 2011
  6. Aug 10, 2011
  7. Aug 09, 2011
  8. Aug 08, 2011
  9. Aug 07, 2011
  10. Aug 05, 2011
  11. Aug 04, 2011
  12. Aug 03, 2011
  13. Aug 02, 2011
  14. Aug 01, 2011
  15. Jul 31, 2011
  16. Jul 30, 2011
  17. Jul 29, 2011
    • Campbell Barton's avatar
    • Campbell Barton's avatar
      pep8 edits and some style change · 3f7e914d
      Campbell Barton authored
      3f7e914d
    • Campbell Barton's avatar
      patch [#27769] Small fixes for X3D exporter: not existing... · 2a9841dc
      Campbell Barton authored
      patch [#27769] Small fixes for X3D exporter: not existing IndexedTriangleSet.creaseAngle, zero Viewpoint.orientation, ...
      
      *Info from the tracker submission this patch resolves*
      
      3. When exporting texture URL, new Blender 2.58 exporter writes URLs in the order: [basename, result of bpy_extras.io_utils.path_reference, absolute]. I propose to change this order to write the result of bpy_extras.io_utils.path_reference *first*. Reasons:
      -- Result of bpy_extras.io_utils.path_reference is controlled by user (through path_mode). By setting it correctly, user can make sure that 1st url matches (which is nice for 3d viewer, also avoids warnings from view3dcene that one url along the way was not available).
      -- This also makes the results of 2.58 exporter more similar to how 2.57 behaved. In 2.57, the relative path "os.path.relpath(filepath_full, relpath)" was first, then basename, then absolute name. And that was good, in my opinion, as relative path has the best chance of success and is more directly controlled by user. (New "bpy_extras.io_utils.path_reference" is even better, so kudos for implementing it.)
      
      4. Finally, a trivial fix to the formatting of output "<TextureTransform..." in X3D. Without this fix, "<TextureTransform" and "translation=" are on the same output line, separated by a lot of whitespaces (taken from ident_step).
      2a9841dc
Loading