Yeah I thought the same but in Processing Android Mode it works this way “loadStrings(“TestStrings.txt”)”, for some reason not sure why? The correct way that we do in Java Mode like this “loadStrings(“data/TestStrings”)”, will give you an error like this.
FATAL EXCEPTION: Animation Thread
Process: processing.test.examplesketch, PID: 5528
java.lang.IllegalArgumentException: File data/TestImage.png contains a path separator
at android.app.ContextImpl.makeFilename(ContextImpl.java:1944)
at android.app.ContextImpl.getFileStreamPath(ContextImpl.java:549)
at android.content.ContextWrapper.getFileStreamPath(ContextWrapper.java:193)
at processing.core.PSurfaceNone.getFileStreamPath(PSurfaceNone.java:317)
at processing.core.PApplet.sketchPath(PApplet.java:5574)
at processing.core.PApplet.createInputRaw(PApplet.java:5099)
at processing.core.PApplet.createInput(PApplet.java:4931)
at processing.core.PApplet.loadImage(PApplet.java:4026)
at processing.test.examplesketch.ExampleSketch.setup(ExampleSketch.java:26)
at processing.core.PApplet.handleDraw(PApplet.java:1846)
at processing.core.PSurfaceNone.callDraw(PSurfaceNone.java:476)
at processing.core.PSurfaceNone$AnimationThread.run(PSurfaceNone.java:516)
Basically it means that there was a path separator and it couldn’t load the image.
Keep in mind all this that I have only just started getting into Processing Android Mode now. Probably someone more experienced knows away to load up files with path separators. I think it might have something to do with “dataPath”, function call? But don’t trust my “dataPath”, theory.