From 81022000063c1fe84d85e8de416d8ab0c2c4c516 Mon Sep 17 00:00:00 2001 From: Bastien Montagne Date: Wed, 16 Jan 2019 19:41:29 +0100 Subject: Cleanup/sanitize usages of G.debug_value. There was no documentation at all, some very bad practices (like using G.debug_value > 0 as some sort of global debug print switch), and even an overlapping use of '1' value... Also, python setter did not check for valid range (since this is a short, not an int). --- source/blender/modifiers/intern/MOD_collision.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'source/blender/modifiers/intern/MOD_collision.c') diff --git a/source/blender/modifiers/intern/MOD_collision.c b/source/blender/modifiers/intern/MOD_collision.c index 011635e3012..7f4a0b91dbf 100644 --- a/source/blender/modifiers/intern/MOD_collision.c +++ b/source/blender/modifiers/intern/MOD_collision.c @@ -141,8 +141,9 @@ static void deformVerts( current_time = DEG_get_ctime(ctx->depsgraph); - if (G.debug_value > 0) + if (G.debug & G_DEBUG_SIMDATA) { printf("current_time %f, collmd->time_xnew %f\n", current_time, collmd->time_xnew); + } mvert_num = mesh_src->totvert; -- cgit v1.2.3