Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- barefists February 2016
- hudson_m4000 January 2016
APMediaPlayer updated to 3.0.1
I've updated APMediaPlayer from APWidgets to work with Processing 3.0.1 for my own project. Was a very minor change (pApplet.getAssets() changed to pApplet.getActivity().getAssets()) If you are interested in using it, you can grab it at GitHub. :)
Tagged:
Comments
Great there will be a lot of happy users
I just looked at the latest updates to Processing-Android in Github, and they're gonna change it again.
This time I see no way to get the current Activity that's running. Which basically means APMediaPlayer can't be used in the next processing release unless they provide a means to access it. I've dropped a comment to the commit to ask for a getter for the Activity instance, hopefully someone reads it.