[Bf-blender-cvs] [e8748e5ae79] soc-2018-bevel: Fixed comment formatting in editmesh.c
Rohan Rathi
noreply at git.blender.org
Sun Aug 5 05:20:09 CEST 2018
Commit: e8748e5ae7955b31c17c6cddb5e092202b39fcfd
Author: Rohan Rathi
Date: Sat Aug 4 22:11:57 2018 +0530
Branches: soc-2018-bevel
https://developer.blender.org/rBe8748e5ae7955b31c17c6cddb5e092202b39fcfd
Fixed comment formatting in editmesh.c
===================================================================
M source/blender/blenkernel/intern/editmesh.c
===================================================================
diff --git a/source/blender/blenkernel/intern/editmesh.c b/source/blender/blenkernel/intern/editmesh.c
index 00e508e4d8f..7d66d25c58a 100644
--- a/source/blender/blenkernel/intern/editmesh.c
+++ b/source/blender/blenkernel/intern/editmesh.c
@@ -251,10 +251,10 @@ void BKE_editmesh_lnorspace_update(BMEditMesh *em)
{
BMesh *bm = em->bm;
- /* We need to create clnors data if none exist yet, otherwise there is no way to edit them. */
- /* Similar code to MESH_OT_customdata_custom_splitnormals_add operator, we want to keep same shading
- * in case we were using autosmooth so far... */
- /* Note: there is a problem here, which is that if someone starts a normal editing operation on previously
+ /* We need to create clnors data if none exist yet, otherwise there is no way to edit them.
+ * Similar code to MESH_OT_customdata_custom_splitnormals_add operator, we want to keep same shading
+ * in case we were using autosmooth so far...
+ * Note: there is a problem here, which is that if someone starts a normal editing operation on previously
* autosmooth-ed mesh, and cancel that operation, generated clnors data remain, with related sharp edges
* (and hence autosmooth is 'lost').
* Not sure how critical this is, and how to fix that issue? */
More information about the Bf-blender-cvs
mailing list