Cleanup: spelling (use 'gimbal' instead of 'gimble')

This commit is contained in:
Campbell Barton 2021-01-04 11:29:11 +11:00
parent 613c568df2
commit c61c7d9926
10 changed files with 17 additions and 17 deletions

View File

@ -1926,7 +1926,7 @@ void BKE_pchan_rot_to_mat3(const bPoseChannel *pchan, float r_mat[3][3])
{
/* rotations may either be quats, eulers (with various rotation orders), or axis-angle */
if (pchan->rotmode > 0) {
/* euler rotations (will cause gimble lock,
/* Euler rotations (will cause gimbal lock,
* but this can be alleviated a bit with rotation orders) */
eulO_to_mat3(r_mat, pchan->eul, pchan->rotmode);
}

View File

@ -77,7 +77,7 @@ bool multires_reshape_assign_final_coords_from_ccg(const MultiresReshapeContext
* not to be updated.
*
* This is a fragile logic, and is only working correctly because the code path is only
* used by sculpt changes. In other usecases the code might not catch inconsistency and
* used by sculpt changes. In other use cases the code might not catch inconsistency and
* silently do wrong decision. */
/* NOTE: There is a known bug in Undo code that results in first Sculpt step
* after a Memfile one to never be undone (see T83806). This might be the root cause of

View File

@ -2873,7 +2873,7 @@ void BKE_object_rot_to_mat3(const Object *ob, float mat[3][3], bool use_drot)
/* rotations may either be quats, eulers (with various rotation orders), or axis-angle */
if (ob->rotmode > 0) {
/* Euler rotations
* (will cause gimble lock, but this can be alleviated a bit with rotation orders). */
* (will cause gimbal lock, but this can be alleviated a bit with rotation orders). */
eulO_to_mat3(rmat, ob->rot, ob->rotmode);
eulO_to_mat3(dmat, ob->drot, ob->rotmode);
}

View File

@ -1776,7 +1776,7 @@ void FONT_OT_text_insert(wmOperatorType *ot)
/** \} */
/* -------------------------------------------------------------------- */
/** \name Textbox Add Operator
/** \name Text-Box Add Operator
* \{ */
static int textbox_add_exec(bContext *C, wmOperator *UNUSED(op))
@ -1817,7 +1817,7 @@ void FONT_OT_textbox_add(wmOperatorType *ot)
/** \} */
/* -------------------------------------------------------------------- */
/** \name Textbox Remove Operator
/** \name Text-Box Remove Operator
* \{ */
static int textbox_remove_exec(bContext *C, wmOperator *op)

View File

@ -1148,7 +1148,7 @@ static ImBuf *icon_preview_imbuf_from_brush(Brush *brush)
BKE_main_blendfile_path_from_global(), path, folder, brush->icon_filepath);
if (path[0]) {
/* use fefault color spaces */
/* Use default color spaces. */
brush->icon_imbuf = IMB_loadiffname(path, flags, NULL);
}
}

View File

@ -655,9 +655,9 @@ static void outliner_add_library_override_contents(SpaceOutliner *soops, TreeEle
int index = 0;
LISTBASE_FOREACH (IDOverrideLibraryProperty *, op, &id->override_library->properties) {
if (!BKE_lib_override_rna_property_find(&idpoin, op, &override_ptr, &override_prop)) {
/* This is fine, override properties list is not alwasy fully up-to-date with current
* RNA/IDProps etc., this gets cleaned up when re-generating the overrides rules, no error
* here. */
/* This is fine, override properties list is not always fully up-to-date with current
* RNA/IDProps etc., this gets cleaned up when re-generating the overrides rules,
* no error here. */
continue;
}

View File

@ -827,14 +827,14 @@ static void viewrotate_apply(ViewOpsData *vod, const int event_xy[2])
quat_to_mat3(m, vod->curr.viewquat);
invert_m3_m3(m_inv, m);
/* Avoid Gimble Lock
/* Avoid Gimbal Lock
*
* Even though turn-table mode is in use, this can occur when the user exits the camera view
* or when aligning the view to a rotated object.
*
* We have gimble lock when the user's view is rotated +/- 90 degrees along the view axis.
* We have gimbal lock when the user's view is rotated +/- 90 degrees along the view axis.
* In this case the vertical rotation is the same as the sideways turntable motion.
* Making it impossible to get out of the gimble locked state without resetting the view.
* Making it impossible to get out of the gimbal locked state without resetting the view.
*
* The logic below lets the user exit out of this state without any abrupt 'fix'
* which would be disorienting.
@ -843,7 +843,7 @@ static void viewrotate_apply(ViewOpsData *vod, const int event_xy[2])
* - Rotated-horizon: `cross_v3_v3v3(xaxis, zvec_global, m_inv[2])`
* When only this is used, this turntable rotation works - but it's side-ways
* (as if the entire turn-table has been placed on its side)
* While there is no gimble lock, it's also awkward to use.
* While there is no gimbal lock, it's also awkward to use.
* - Un-rotated-horizon: `m_inv[0]`
* When only this is used, the turntable rotation can have gimbal lock.
*
@ -852,7 +852,7 @@ static void viewrotate_apply(ViewOpsData *vod, const int event_xy[2])
* Blending isn't essential, it just makes the transition smoother.
*
* This allows sideways turn-table rotation on a Z axis that isn't world-space Z,
* While up-down turntable rotation eventually corrects gimble lock. */
* While up-down turntable rotation eventually corrects gimbal lock. */
#if 1
if (len_squared_v3v3(zvec_global, m_inv[2]) > 0.001f) {
float fac;

View File

@ -868,7 +868,7 @@ static bool joint_callback(const iTaSC::Timestamp &timestamp,
float rmat[3][3];
if (chan->rotmode > 0) {
/* euler rotations (will cause gimble lock, but this can be alleviated a bit with rotation
/* Euler rotations (will cause gimbal lock, but this can be alleviated a bit with rotation
* orders) */
eulO_to_mat3(rmat, chan->eul, chan->rotmode);
}

View File

@ -39,7 +39,7 @@ static void execute_on_component(const GeoNodeExecParams &params, GeometryCompon
const std::string result_name = params.get_input<std::string>("Result");
/* Once we support more domains at the user level, we have to decide how the result domain is
* choosen. */
* chosen. */
const AttributeDomain result_domain = ATTR_DOMAIN_POINT;
const CustomDataType result_type = CD_PROP_COLOR;

View File

@ -95,7 +95,7 @@ static float point_weight_influence_get(const float maximum_distance,
* Weight each point based on their proximity to its neighbors
*
* For each index in the weight array add a weight based on the proximity the
* corresponding point has with its neighboors.
* corresponding point has with its neighbors.
**/
static void points_distance_weight_calculate(Vector<float> *weights,
const size_t point_id,