Thanks a lot for the support.

Regards.

On Jun 9, 1:53 pm, Ravi <yend...@pv.com> wrote:
> Please look at the API "private boolean seekMethod1(int keyCode)" in
> MediaPlaybackActivity.java.
>
> -Ravi
>
> On Jun 9, 12:05 pm, Alex_26 <alexgarci...@gmail.com> wrote:
>
>
>
> > Thanks for the reply.
>
> > The ones from the first row on zoom2 hardware (QWERTY....). Also
> > backspace to pause. That is what I thought but I just need
> > confirmation. Do you know which file has event handler for the
> > keyboard in the music player ?
>
> > On Jun 9, 11:39 am, Ravi <yend...@pv.com> wrote:
>
> > > OpenCORE does not have a direct dependency on any keys on the physical/
> > > virtual keyboard. That being said, applications can react to certain
> > > key events and take action accordingly.
>
> > > What are the keys that make the mediaplayer FF/Rew ?
>
> > > -Ravi
>
> > > On Jun 9, 10:29 am, Alex_26 <alexgarci...@gmail.com> wrote:
>
> > > > Hi. This is probably a silly question but I just need confirmation. In
> > > > the music player application in Opencore 2.0 we had a test case were
> > > > pressing 150 short keys should not result in any strange behavior in
> > > > the audio playback. Now the testing team has reported that in opencore
> > > > 2.04 when you press certain keys a fast forward or rewind (depending
> > > > on the key) in the playback is seen. I think this is expected so the
> > > > user does not depend on the touchscreen to make seek operations.
>
> > > > Can someone confirm if this is expected behavior for the music player
> > > > in Opencore 2.04?
>
> > > > Thanks!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to 
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to