I believe we were able to do the fixes for SoundPool without changing
the public API. There are no plans to deprecate it at this time.
On Feb 16, 6:05 am, "Blake B." wrote:
> Great idea, Jon. Thanks for sharing the code. I'm about to start
> work on sound in my game, so I'll look into using th
Great idea, Jon. Thanks for sharing the code. I'm about to start
work on sound in my game, so I'll look into using this.
Hopefully, Google realizes that many are using SoundPool and will keep
the existing API in place for a while, even if deprecated, long enough
to migrate apps. I think we are
On Feb 16, 6:25 am, Marco Nelissen wrote:
> Why do you say it's not a public API?
"SoundPool is undocumented because it is not ready as a public API and
is subject to change."
http://groups.google.com/group/android-developers/msg/6c360f2d0662be0a
--
Jon
--~--~-~--~~~--
Why do you say it's not a public API?
On Sun, Feb 15, 2009 at 10:09 PM, Jon Colverson wrote:
> The presence of SoundPool in the SDK causes a bit of a dilemma for
> those of us developing games. On the one hand, it's not a public API
> and it might go away or change in future releases, breaking
4 matches
Mail list logo
