Cleanup: Spelling/grammar in comments
This commit is contained in:
parent
1d9bac7d92
commit
c0fb8ea8f3
|
@ -113,7 +113,7 @@ struct KeyBlock *BKE_keyblock_find_name(struct Key *key, const char name[]);
|
|||
void BKE_keyblock_copy_settings(struct KeyBlock *kb_dst, const struct KeyBlock *kb_src);
|
||||
/**
|
||||
* Get RNA-Path for 'value' setting of the given shape-key.
|
||||
* \note the user needs to free the returned string once they're finish with it.
|
||||
* \note the user needs to free the returned string once they're finished with it.
|
||||
*/
|
||||
char *BKE_keyblock_curval_rnapath_get(struct Key *key, struct KeyBlock *kb);
|
||||
|
||||
|
|
|
@ -48,7 +48,7 @@
|
|||
* Ideally this could be could be even closer to Python's enumerate(). We might get that in the
|
||||
* future with newer C++ versions.
|
||||
*
|
||||
* One other important feature is the as_span method. This method returns an Span<int64_t>
|
||||
* One other important feature is the as_span method. This method returns a Span<int64_t>
|
||||
* that contains the interval as individual numbers.
|
||||
*/
|
||||
|
||||
|
|
|
@ -62,7 +62,7 @@
|
|||
* then the function has to specify whether the referenced array is expected to be initialized or
|
||||
* not.
|
||||
*
|
||||
* Since the arrays are only referenced, it is generally unsafe to store an Span. When you
|
||||
* Since the arrays are only referenced, it is generally unsafe to store a Span. When you
|
||||
* store one, you should know who owns the memory.
|
||||
*
|
||||
* Instances of Span and MutableSpan are small and should be passed by value.
|
||||
|
|
|
@ -263,7 +263,7 @@ class VectorSet {
|
|||
}
|
||||
|
||||
/**
|
||||
* Get an Span referencing the keys vector. The referenced memory buffer is only valid as
|
||||
* Get a Span referencing the keys vector. The referenced memory buffer is only valid as
|
||||
* long as the vector set is not changed.
|
||||
*
|
||||
* The keys must not be changed, because this would change their hash value.
|
||||
|
|
|
@ -104,7 +104,7 @@ typedef struct UndoMesh {
|
|||
int selectmode;
|
||||
|
||||
/** \note
|
||||
* this isn't a prefect solution, if you edit keys and change shapes this works well
|
||||
* This isn't a perfect solution, if you edit keys and change shapes this works well
|
||||
* (fixing T32442), but editing shape keys, going into object mode, removing or changing their
|
||||
* order, then go back into editmode and undo will give issues - where the old index will be
|
||||
* out of sync with the new object index.
|
||||
|
|
|
@ -1445,7 +1445,7 @@ static void rna_def_ID_properties(BlenderRNA *brna)
|
|||
RNA_def_struct_refine_func(srna, "rna_PropertyGroup_refine");
|
||||
|
||||
/* important so python types can have their name used in list views
|
||||
* however this isn't prefect because it overrides how python would set the name
|
||||
* however this isn't perfect because it overrides how python would set the name
|
||||
* when we only really want this so RNA_def_struct_name_property() is set to something useful */
|
||||
prop = RNA_def_property(srna, "name", PROP_STRING, PROP_NONE);
|
||||
RNA_def_property_flag(prop, PROP_IDPROPERTY);
|
||||
|
|
|
@ -99,7 +99,7 @@ static void pygpu_fill_format_sequence(void *data_dst_void,
|
|||
PyObject **value_fast_items = PySequence_Fast_ITEMS(py_seq_fast);
|
||||
|
||||
/**
|
||||
* Args are constants, so range checks will be optimized out if they're nop's.
|
||||
* Args are constants, so range checks will be optimized out if they're no-op's.
|
||||
*/
|
||||
#define PY_AS_NATIVE(ty_dst, py_as_native) \
|
||||
ty_dst *data_dst = data_dst_void; \
|
||||
|
|
|
@ -1140,7 +1140,7 @@ void WM_redraw_windows(bContext *C)
|
|||
* This is needed for viewport drawing for operator use
|
||||
* (where the viewport may not have drawn yet).
|
||||
*
|
||||
* Otherwise avoid using these sine they're exposing low level logic externally.
|
||||
* Otherwise avoid using these since they're exposing low level logic externally.
|
||||
*
|
||||
* \{ */
|
||||
|
||||
|
|
Loading…
Reference in New Issue