On my Pi 4 if I start Purr Data from command line with:
everything is fine with my preferences as I last saved them, but if I use the following systemd service to start Purr Data the prefs are always defaulted to scratch settings. Why is this the case and what might be the solution?
I've tested two separate touchscreens on a Pi 3B+ (Raspbian Stretch) running Pd-l2ork-2.5.1. One screen is a 5" resistive (https://www.adafruit.com/product/2260) and one is a 7" capacitive (https://www.waveshare.com/7inch-hdmi-lcd-c.htm). They both connect with an HDMI cable, and a USB cable for touch.
The resistive screen operates as expected. I can slide my finger to operate an hslider. I can use the cursor object and see x/y parameters as I slide my finger in a patch.
The capacitive screen operates differently. I have to tap the screen to operate an hslider. I can't slide it. Also, the cursor object only shows x/y as I tap the screen, not as I slide on it even though the screen cursor is moving along directly under my finger as I slide it. The hid object with this touchscreen shows absolute x/y but hid is a very expensive object when polled fast enough for what I need, and it'd be a lot cleaner for me to have the touchscreen work directly with sliders.
Does anybody have any suggestions how I could filter or transform the interaction between pd and the capacitive screen so it's like the resistive screen? It's strange because the onscreen cursor moves just as if a mouse is moving it but pd doesn't recognize it unless I'm tapping instead of sliding.
Thank you for any insight.
Cyclone library objects like buddy and coll can be created on the Pi3 (Purr Data 2.3.2 Raspbian) but others like uzi and bucket cannot be created for some reason. All of the above objects can be created in Purr Data 2.3.2 on OS X 10.10.5 however. Did some Cyclone objects not make it to Raspbian or is there something else I should install to make them available?
Thanks, guys! @jancsika Your approach is exactly what I was looking for, and it works on Raspbian.
Slight follow up:
- Can I get that code to execute automatically somehow as a script instead of typing it into the DevTools Console every time?
- Is there a similar method to remove the side and bottom scrollbars?
@jancsika My goal is to be able to use all 800 x 480 pixels for the GUI patch I'm creating with Purr Data on a Pi3 with 5" HDMI touchscreen. That strip across the top (the menubar) is valuable real estate that I can't currently use, and also, the menubar options will be irrelevant to the final functionality of the patch. Everything else is going very well functionality-wise. Is there any message I could send to the window or to pd or any other technique to hide the menubar or cover it? It'd be useful to be able to toggle the menubar on and off during development. I could deal with just hiding or covering it if that were the only option though.
When I choose View>Fullscreen in Purr Data on OS X Yosemite my patch goes all the way to all four edges of the screen, but in Raspbian on a Pi3 the File-Edit menubar options stay across the top when I choose View>Fullscreen. Is there any way of hiding that and getting my patch to dominate the whole screen?