1 files changed, 0 insertions, 42 deletions
diff --git a/externals/build/doc/linuxmouse-help.pd b/externals/build/doc/linuxmouse-help.pd
deleted file mode 100644
index 067733a4..00000000
--- a/externals/build/doc/linuxmouse-help.pd
+++ /dev/null
@@ -1,42 +0,0 @@
-#N canvas 112 187 450 441 10;
-#X floatatom 238 220 5 0 0 3 button# - -;
-#X floatatom 299 220 5 0 0 3 button_value - -;
-#X floatatom 190 220 2 0 0 3 wheel - -;
-#X floatatom 137 220 4 0 0 3 y-axis - -;
-#X floatatom 79 220 4 0 0 3 x-axis - -;
-#X obj 95 193 linuxmouse /dev/input/event0;
-#X obj 18 6 cnv 15 400 30 empty empty linuxmouse 20 12 1 16 -225280
--66577 0;
-#X text 206 17 related HID objects:;
-#X obj 357 16 linuxhiderfic;
-#X text 24 263 [linuxmouse] takes events directly from a Linux event
-device \, so that you get mouse data regardless of whether Pd has focus.
-Also \, the data from the event system is relative and limited to the
-screen size.;
-#X msg 51 71 start;
-#X msg 51 93 stop;
-#X msg 115 70 poll;
-#X msg 115 92 nopoll;
-#X text 24 335 Rather than polling like the other linuxhid objects
-\, [linuxmouse] uses a pollfn so it receives events as they happen.
-A pollfn listens to a network socket \, and takes action upon activity.
-Since all mouse events go through the network socket between pd and
-pd-gui \, this works for responding to mouse events.;
-#X msg 158 165 close;
-#X text 179 91 (synonyms for the same actions);
-#X text 182 75 start/stop polling;
-#X msg 147 122 open;
-#X msg 152 142 open /dev/input/event1;
-#X text 183 123 opens the previous device;
-#X connect 5 0 4 0;
-#X connect 5 1 3 0;
-#X connect 5 2 2 0;
-#X connect 5 3 0 0;
-#X connect 5 4 1 0;
-#X connect 10 0 5 0;
-#X connect 11 0 5 0;
-#X connect 12 0 5 0;
-#X connect 13 0 5 0;
-#X connect 15 0 5 0;
-#X connect 18 0 5 0;
-#X connect 19 0 5 0;