1 files changed, 33 insertions, 0 deletions
diff --git a/externals/gridflow/doc/flow_classes/usertime-help.pd b/externals/gridflow/doc/flow_classes/usertime-help.pd
new file mode 100644
index 00000000..28d52a2c
--- /dev/null
+++ b/externals/gridflow/doc/flow_classes/usertime-help.pd
@@ -0,0 +1,33 @@
+#N canvas 508 124 632 412 10;
+#X obj 0 0 doc_h;
+#X obj 3 177 doc_c;
+#X obj 0 383 doc_f;
+#X obj 3 363 doc_also;
+#X obj 103 363 cputime;
+#X obj 157 363 systemtime;
+#X text 186 108 What [usertime] and [systemtime] tell you together
+should add up to the amount that [cputime] tells you.;
+#X obj 3 301 doc_o 1;
+#X obj 3 217 doc_i 2;
+#X obj 14 247 doc_ii 0;
+#X obj 14 269 doc_ii 1;
+#X obj 14 331 doc_oo 0;
+#X obj 97 247 doc_m i0 bang;
+#X obj 97 269 doc_m i1 bang;
+#X obj 97 331 doc_m o0 float;
+#X text 232 247 reset timer;
+#X text 232 269 trigger output;
+#X text 232 331 value in milliseconds;
+#X text 188 142 In C language \, this is the "utime" feature of the
+times() command.;
+#X obj 61 66 usertime;
+#X text 188 38 While [cputime] gives you the total time spent in the
+pd process \, therefore excluding any time spent running any other
+programmes \, time spent running pd.tk \, and time spent doing nothing
+at all \, [systemtime] also excludes whatever is run in the kernel.
+;
+#X connect 3 1 4 0;
+#X connect 3 1 5 0;
+#X connect 12 1 15 0;
+#X connect 13 1 16 0;
+#X connect 14 1 17 0;