Acknowledged
5 months ago

API Request - functions that allow an app to specify the start and end of an activity

This would solve this issue: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-7-series/308450/bug-long-press-back-button-issue-still-not-fixed-in-fw9-33 and https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/epix-2/334122/bug---epix2-marq2-f7-long-press-of-back-button-from-an-app-does-not-terminate-it-properly-when-no-activity-is-running#pifragment-1292=1

If an app is not running an activity then a long press back should terminate it so that if long press back is set to "show watch face" the Back and Start buttons function consistently with builtin apps that do not start activities, like Maps and all built-in glances.

pstoppani
Parents
  • over 2 years ago

    IOW, 945 LTE already behaves the way you want, without any changes to the CIQ API.

    API changes would only be necessary if Garmin wanted an app to be able to respond somehow to a "request to return to watchface via hotkey" and choose whether to terminate or not. I doubt they want to add that kind of complexity and freedom to the api.

    If we're saying that CIQ apps should act like native apps, then most native apps (which map to sports) are really only "active" once recording has started (i.e. the user has pressed START to initialize a recording, and they haven't terminated the current recording by saving or discarding the activity.) In the same way, we could say that a CIQ app is only "active" (in terms of an "activity") when it's actually recording an activity.

    Ofc this would exclude a whole class of apps that have some concept of a "session" or "activity", but they just don't record anything.

Comment
  • over 2 years ago

    IOW, 945 LTE already behaves the way you want, without any changes to the CIQ API.

    API changes would only be necessary if Garmin wanted an app to be able to respond somehow to a "request to return to watchface via hotkey" and choose whether to terminate or not. I doubt they want to add that kind of complexity and freedom to the api.

    If we're saying that CIQ apps should act like native apps, then most native apps (which map to sports) are really only "active" once recording has started (i.e. the user has pressed START to initialize a recording, and they haven't terminated the current recording by saving or discarding the activity.) In the same way, we could say that a CIQ app is only "active" (in terms of an "activity") when it's actually recording an activity.

    Ofc this would exclude a whole class of apps that have some concept of a "session" or "activity", but they just don't record anything.

Children
No Data