Cleanup: spelling in comments
This commit is contained in:
@@ -4066,19 +4066,19 @@ void BLO_main_expander(BLOExpandDoitCallback expand_doit_func)
|
||||
static int expand_cb(LibraryIDLinkCallbackData *cb_data)
|
||||
{
|
||||
/* Embedded IDs are not known by lib_link code, so they would be remapped to `nullptr`. But there
|
||||
* is no need to process them anyway, asthey are already handled during the 'read_data' phase.
|
||||
* is no need to process them anyway, as they are already handled during the 'read_data' phase.
|
||||
*/
|
||||
if (cb_data->cb_flag & (IDWALK_CB_EMBEDDED | IDWALK_CB_EMBEDDED_NOT_OWNING)) {
|
||||
return IDWALK_RET_NOP;
|
||||
}
|
||||
|
||||
/* Explicitely requested to be ignored during readfile processing. Means the read_data code
|
||||
/* Explicitly requested to be ignored during readfile processing. Means the read_data code
|
||||
* already handled this pointer. Typically, the 'owner_id' pointer of an embedded ID. */
|
||||
if (cb_data->cb_flag & IDWALK_CB_READFILE_IGNORE) {
|
||||
return IDWALK_RET_NOP;
|
||||
}
|
||||
|
||||
/* Expand process can be re-entrant or have other complex imteractions that will not work well
|
||||
/* Expand process can be re-entrant or have other complex interactions that will not work well
|
||||
* with loop-back pointers. Further more, processing such data should not be needed here anyway.
|
||||
*/
|
||||
if (cb_data->cb_flag & (IDWALK_CB_LOOPBACK)) {
|
||||
|
||||
@@ -394,7 +394,7 @@ struct EraseOperationExecutor {
|
||||
* For each point in the source, the corresponding vector in \a src_to_dst_points contains a set
|
||||
* of destination points (PointTransferData), which can correspond to points of the source, or
|
||||
* linear combination of them. Note that this vector can be empty, if we want to remove points
|
||||
* for example. Curves can also be splitted if a destination point is marked as a cut.
|
||||
* for example. Curves can also be split if a destination point is marked as a cut.
|
||||
*
|
||||
* \returns an array containing the same elements as \a src_to_dst_points, but in the destination
|
||||
* points domain.
|
||||
|
||||
@@ -106,7 +106,7 @@ typedef struct IDPropertyUIDataString {
|
||||
typedef struct IDPropertyUIDataID {
|
||||
IDPropertyUIData base;
|
||||
/**
|
||||
* #ID_Type. With python-defined propoerties, this type is not enforced. A value of `0` means any
|
||||
* #ID_Type. With python-defined properties, this type is not enforced. A value of `0` means any
|
||||
* ID type.
|
||||
*
|
||||
* However, when defined/edited from the UI (Custom Properties panel), it must/will be defined,
|
||||
|
||||
Reference in New Issue
Block a user