kannonier8/blender
1
0
Fork 0
forked from bartvdbraak/blender
Code Pull Requests Activity

Fixed a couple of typos in the Python API docs

Browse Source
This commit is contained in:
Howard Trickey 2012-03-23 14:29:59 +00:00
parent 87681b46ea
commit ef1d3a3993
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/python_api/rst/include__bmesh.rst
View File

@ -110,10 +110,10 @@ Keeping a Correct State
When modeling in blender there are certain assumptions made about the state of the mesh.
* hidden geometry isn't selected.
* when an edge is selected, its vertices's are selected too.
* when a face is selected, its edges and vertices's are selected.
* when an edge is selected, its vertices are selected too.
* when a face is selected, its edges and vertices are selected.
* duplicate edges / faces don't exist.
* faces have at least 3 vertices's.
* faces have at least 3 vertices.
To give developers flexibility these conventions are not enforced,
however tools must leave the mesh in a valid state else other tools may behave incorrectly.

2
doc/python_api/rst/info_best_practice.rst
View File

@ -268,7 +268,7 @@ The **try** statement is useful to save time writing error checking code.
However **try** is significantly slower then an **if** since an exception has to be set each time, so avoid using **try** in areas of your code that execute in a loop and runs many times.
There are cases where using **try** is faster than checking weather the condition will raise an error, so it is worth experimenting.
There are cases where using **try** is faster than checking whether the condition will raise an error, so it is worth experimenting.
Value Comparison

4
doc/python_api/rst/info_gotcha.rst
View File

@ -155,7 +155,7 @@ Support Overview
+==============+==============================+================================+================================+
|Import/Create |Bad (inflexible) |Fine (supported as upgrade path)|Best |
+--------------+------------------------------+--------------------------------+--------------------------------+
|Manipulate |Bad (inflexible) |Bad (looses ngons) |Best |
|Manipulate |Bad (inflexible) |Bad (loses ngons) |Best |
+--------------+------------------------------+--------------------------------+--------------------------------+
|Export/Output |Good (ngons) |Good (When ngons can't be used) |Good (ngons, memory overhead) |
+--------------+------------------------------+--------------------------------+--------------------------------+
@ -188,7 +188,7 @@ Editing is where the 3 data types vary most.
Exporting
---------
All 3 data types can be used for exporting, the choice mostly depends on weather the target format supports ngons or not.
All 3 data types can be used for exporting, the choice mostly depends on whether the target format supports ngons or not.
* polygons are the most direct & efficient way to export providing they convert into the output format easily enough.
* tessfaces work well for exporting to formats which dont support ngons, in fact this is the only place where their use is encouraged.