Ticket Created
over 5 years ago

WERETECH-7661

WERETECH-7662

WERETECH-7663

WERETECH-7853

WERETECH-7854

Assorted Media Player Button Bugs Across Devices

I've been experimenting with some of the media player button handling code across different devices and run into a few issues. Below is a table which summarizes my findings.

For context, Runcasts currently implements fast-forward/rewind using some pretty crazy hacks which re-map the skip-previous / skip-next buttons into changing the ActiveContent playhead. Needless to say, I'd love to strip that code out and use the normal approach. Unfortunately, the various options below all suffer some drawback on one of the devices we're trying to support.

Feature Vivoactive3 Button-Based Button-Based Hotkey
SystemButton BUG [1] OK OK
CustomButton OK OK BUG [2]
PLAYBACK_CONTROL_SKIP_BACKWARD/FORWARD BUG [3] OK [4] OK
  1. Image doesn't show, button doesn't work              
  2. Image shows, button event doesn't fire when clicked                    
  3. Crashes, no CIQ.YML generated
  4. Not a bug per-se, but a record-scratch occurs during skip, hacks to implement fast-forward/rewind avoid the record-scratch sound (at the expense of being slightly delayed when starting) 

rconradharris
Parents
  • over 5 years ago in reply to Stephen.ConnectIQ

    Former Member

    Thanks for the update. For #1, I'm trying to use SystemButton to replace the icon for the NEXT/PREVIOUS buttons with icons that look like FWD/BKWD buttons.

    The goal here is to essentially hide from the user that the feature is implemented by remapping the NEXT/PREVIOUS buttons: by changing the icon, the user will just see a FWD/BKWD button, click it, and it will move the playhead. They don't have to know that under-the-hood, it's really just the next/previous button with a whole bunch of hacky code attached Slight smile

    So the scenario I'm trying to set up on the VV3 is:

    <PREV (BKWD icon)> <PLAY> <NEXT (FWD icon)>

        <VOLUME> <...>

    When I do this however, I end up with a blank image on the VV3 (while the image shows correctly on the BB watches).

    RE: simulator issues. I basically don't use the simulator for development: it's mostly unusable for serious music player development: too many crashes and differences with devices. I'll occasionally smoke-test using it, or maybe use it to test out some networking code, but anything related to playback controls (especially finnicky device dependent code), I just do on the watch themselves.

Comment
  • over 5 years ago in reply to Stephen.ConnectIQ

    Former Member

    Thanks for the update. For #1, I'm trying to use SystemButton to replace the icon for the NEXT/PREVIOUS buttons with icons that look like FWD/BKWD buttons.

    The goal here is to essentially hide from the user that the feature is implemented by remapping the NEXT/PREVIOUS buttons: by changing the icon, the user will just see a FWD/BKWD button, click it, and it will move the playhead. They don't have to know that under-the-hood, it's really just the next/previous button with a whole bunch of hacky code attached Slight smile

    So the scenario I'm trying to set up on the VV3 is:

    <PREV (BKWD icon)> <PLAY> <NEXT (FWD icon)>

        <VOLUME> <...>

    When I do this however, I end up with a blank image on the VV3 (while the image shows correctly on the BB watches).

    RE: simulator issues. I basically don't use the simulator for development: it's mostly unusable for serious music player development: too many crashes and differences with devices. I'll occasionally smoke-test using it, or maybe use it to test out some networking code, but anything related to playback controls (especially finnicky device dependent code), I just do on the watch themselves.

Children
No Data