Cleanup: fix typos in doc subdirectory
Fix several documentation related typos. Found via `codespell -S "*.desktop,*.diff,./intern,./extern,./locale,./AUTHORS,./source/blender/blenlib/tests/BLI_string_utf8_test.cc,./doc/license/bf-members.txt" -L accessort,abd,aci,alo,ans,ba,bording,childrens,clen,constructin,datas,dependees,domin,eary,ege,eiter,elemt,eles,endianess,enew,espace,finded,fiter,fpt,groupd,hist,implementating,indext,ine,infront,inout,inouts,inpt,ist,lene,listenter,lod,maks,masia,mata,mis,mke,nam,nd,ned,opose,ot,outlow,parm,parms,passt,pinter,pixelx,poin,pres,ptd,re-usable,re-use,re-used,re-uses,re-using,ridiculus,schem,soler,strack,suh,te,tesselate,tham,ue,vai,varius,wew` Pull Request: https://projects.blender.org/blender/blender/pulls/145824
This commit is contained in:
@@ -67,7 +67,7 @@ Contents
|
|||||||
serve as permanent little button-fields in Blender windows. Think for example of having
|
serve as permanent little button-fields in Blender windows. Think for example of having
|
||||||
an (optional) extra field in the 3d window displaying object loc/rot/size.
|
an (optional) extra field in the 3d window displaying object loc/rot/size.
|
||||||
After that, the existing button windows can be reorganized in such blocks as well, allowing
|
After that, the existing button windows can be reorganized in such blocks as well, allowing
|
||||||
a user to configure the genereal buttons layout (make vertical for example).
|
a user to configure the general buttons layout (make vertical for example).
|
||||||
|
|
||||||
|
|
||||||
--------------1.1 C and H files
|
--------------1.1 C and H files
|
||||||
@@ -263,10 +263,10 @@ uiBut *UiDefBut[CSIF]( uiBlock *block, int type, int retval, char *str,
|
|||||||
short x1, short y1, short x2, short y2, xxxx *poin,
|
short x1, short y1, short x2, short y2, xxxx *poin,
|
||||||
float min, float max, float a1, float a2, char *tip)
|
float min, float max, float a1, float a2, char *tip)
|
||||||
|
|
||||||
UiDefButC operatates on char
|
UiDefButC operates on char
|
||||||
UiDefButS operatates on short
|
UiDefButS operates on short
|
||||||
UiDefButI operatates on int
|
UiDefButI operates on int
|
||||||
UiDefButF operatates on float
|
UiDefButF operates on float
|
||||||
|
|
||||||
*block: current uiBlock pointer
|
*block: current uiBlock pointer
|
||||||
type: see below
|
type: see below
|
||||||
|
|||||||
@@ -106,7 +106,7 @@ print("test_array:", tuple(scene.test_array))
|
|||||||
|
|
||||||
# Boolean array, using 'transform' accessors.
|
# Boolean array, using 'transform' accessors.
|
||||||
# Note how the same result is achieved as with previous get/set example, but using default RNA storage.
|
# Note how the same result is achieved as with previous get/set example, but using default RNA storage.
|
||||||
# Transform accessors also have access to more informations.
|
# Transform accessors also have access to more information.
|
||||||
# Also note how the stored data _is_ a two-items array.
|
# Also note how the stored data _is_ a two-items array.
|
||||||
# - Set function stores a single boolean value, returned as the second component.
|
# - Set function stores a single boolean value, returned as the second component.
|
||||||
# - Array getters must return a list or tuple.
|
# - Array getters must return a list or tuple.
|
||||||
|
|||||||
@@ -15,7 +15,7 @@ Typically, Python objects representing (wrapping) Blender data have a limited li
|
|||||||
They are created on-demand, and deleted as soon as they are not used in Python anymore.
|
They are created on-demand, and deleted as soon as they are not used in Python anymore.
|
||||||
|
|
||||||
This means that storing python-only data in these objects should not be done for anything that
|
This means that storing python-only data in these objects should not be done for anything that
|
||||||
requires some form of persistance.
|
requires some form of persistence.
|
||||||
|
|
||||||
There are some exceptions to this rule. For example, IDs do store their Python instance, once created,
|
There are some exceptions to this rule. For example, IDs do store their Python instance, once created,
|
||||||
and re-use it instead of re-creating a new Python object every time they are accessed from Python.
|
and re-use it instead of re-creating a new Python object every time they are accessed from Python.
|
||||||
|
|||||||
Reference in New Issue
Block a user