I’m not alone. There are others who’ve experienced the same failed build as an Error from inside the Android tools, check the console with Processing 2.1? or an Android java issue. Some have solved the issue. I haven’t. Even the working through the processing android instructions and getting busy in the terminal to make it easier to examine the file system hasn’t resulted in a successful build.
The experience was incredible. It was if I’d just stepped into the wonderful world of Oz. The experience was remarkably like Dorothy tapping her shiny red shoes wishing hwe returning to Kansas. There I was tapping the screen of my mobile phone, just like Dorothy tapping her shoes and wishing to be whisked away to a familiar place. Unlike Dorothy leaving the fantastical colourful world of Oz for a mundane existence in Kansas, I was leaving the mundane world of default settings for the colourful and exciting world of developer options. A developer world previously available to Android users by default, but now had been obfuscated behind a a mysterious and unnecessary iron curtain. An world that would only become available after tapping the screen of my device seven times. Bizarre.
My questions for hTC
- Why would you ever think your users would never be interested in accessing functionality offered by developer options by default?
- Why would you think it would be better to make it more difficult rather than less difficult for users to attempt to develop tools and content with and for their phone?
- What was your reason for doing this and why seven taps?
I’m having trouble with the surfaceTouchEvent in the Responding to touch interaction recipe from the Processing 2 Creative programming cookbook source code on GitHub.
I’ve worked through the Troubleshooting, Discussion and Known issues, Common problems, Understanding changes to processing.core sections of the Android page of the Processing Wiki, but still no success.
Unsurprisingly, someone else posted a similar issue with Android Multitouch on Processing 2.0.X on the Android Processing Forum. Unfortunately their solution (import. android.view.motionEvent) doesn’t seem to resolve my issue.
Time to sort this one out.
Inspired by Tom Woodwards’s Dune-themed tweet on 24 April 2014, Rhys Fulber and Bill Leeb’s production on Fear Factory’s Fear Is the Mindkiller EP and the Bene Gesserit’s litany against fear and based on Jan Vantomme’s Drawing text and Running your sketch on an Android device Processing recipes on Github, I created this portable litany against fear as a fun exercise in combining , expanding and learning further from the recipes I’ve worked through so far.
Extending the functionality
I’d like to extend the portable litany against fear by creating functionality that allows for use of:
- sound by including pre-loaded audio samples that play as each line of the litany is displayed
- custom text and audio affirmations to be entered by users
- events such as display of text and playing of audio or other events to be triggered by touching and swiping of screen by the user.