Bugfix [#29125] Motion paths odd behaviour

* Made it impossible to try to calculate/create new motion paths lasting 0
frames (i.e. 250 to 250) since we cannot allocate a zero-length array for these.
Start frame can now be at most end-frame - 1, and end frame at least start frame
+ 1

* If an invalid configuration does occur, warnings/reports will now be issued in
response to this instead of silently failing (as per this bugreport).

1 files changed, 3 insertions, 2 deletions

diff --git a/source/blender/makesrna/intern/rna_animviz.c b/source/blender/makesrna/intern/rna_animviz.c
index e65b137e846..29133db8101 100644
--- a/source/blender/makesrna/intern/rna_animviz.c
+++ b/source/blender/makesrna/intern/rna_animviz.c
@@ -71,7 +71,7 @@ static void rna_AnimViz_path_start_frame_set(PointerRNA *ptr, int value)
 {
 	bAnimVizSettings *data= (bAnimVizSettings*)ptr->data;
 	
-	CLAMP(value, 1, data->path_ef);
+	CLAMP(value, 1, data->path_ef-1);
 	data->path_sf= value;
 }
 
@@ -79,7 +79,8 @@ static void rna_AnimViz_path_end_frame_set(PointerRNA *ptr, int value)
 {
 	bAnimVizSettings *data= (bAnimVizSettings*)ptr->data;
 	
-	CLAMP(value, data->path_sf, (int)(MAXFRAMEF/2));
+	// XXX: watchit! Path Start > MAXFRAME/2 could be a problem...
+	CLAMP(value, data->path_sf+1, (int)(MAXFRAMEF/2));
 	data->path_ef= value;
 }