Print out reports on console too (debug and up) as fix for [#26708] "INFO" reports...
authorNathan Letwory <nathan@letworyinteractive.com>
Sat, 9 Apr 2011 02:23:39 +0000 (02:23 +0000)
committerNathan Letwory <nathan@letworyinteractive.com>
Sat, 9 Apr 2011 02:23:39 +0000 (02:23 +0000)
reported by Tom Edwards

Showing of certain reports (ie. info) is very hidden. At least print these to console.

source/blender/windowmanager/intern/wm_event_system.c

index e3d2a738497be090f6bac42829f47434ea9f44b8..2b74d35d59e55c94e319a25a4d10002ff40dfdd6 100644 (file)
@@ -445,6 +445,7 @@ static void wm_operator_reports(bContext *C, wmOperator *op, int retval, int pop
                if(G.f & G_DEBUG)
                        wm_operator_print(C, op); /* todo - this print may double up, might want to check more flags then the FINISHED */
                
+               BKE_reports_print(op->reports, RPT_DEBUG); /* print out reports to console. */
                if (op->type->flag & OPTYPE_REGISTER) {
                        if(G.background == 0) { /* ends up printing these in the terminal, gets annoying */
                                /* Report the python string representation of the operator */
@@ -705,7 +706,6 @@ static int wm_operator_invoke(bContext *C, wmOperatorType *ot, wmEvent *event, P
                if (!(retval & OPERATOR_HANDLED) && retval & (OPERATOR_FINISHED|OPERATOR_CANCELLED))
                        /* only show the report if the report list was not given in the function */
                        wm_operator_reports(C, op, retval, (reports==NULL));
-                       
                
                if(retval & OPERATOR_HANDLED)
                        ; /* do nothing, wm_operator_exec() has been called somewhere */