Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Touch setting bug.

Paulr707
over 1 year ago

While trying to adjust the touch settings to a way that works for me I noticed an anomaly.

The touch setting for some activities does not work. One example is the "Map" activity. This follows the general use setting for touch rather than the Map activity touch setting - so if the general use setting is off but the map touch setting is on (as I have it set), touch doesn't work for the map activity as expected.

After some experimentation I think I've spotted what's going on. For most activities like "Run" or "Walk", the touch setting for Run and walk only come into play once the activity is actually started. While the activity is in the preview stage (while getting GPS lock etc) the touch setting for "General Use" touch setting is used. (this is probably the bug?). For most activities this doesn't matter as you usually press the start button soon after to set the timer running etc. But for some "Activities" like "Map", the start button has no meaning so it's always in the preview phase.

I think the fix should be to make all activities observe the touch setting for the activity while in the activity preview stage (timer not running).

I see this has been reported before in various ways but I don't think anyone made the connection that the touch setting for an activity only works if the timer for that activity is running. e.g.

forums.garmin.com/.../15-19-bug-touch-not-working-in-maps-if-general-use-touch-is-off

I'm on FW 17.26

  • 0 over 1 year ago

    Good find! I think you should report a separate bug. TBH, I feel like Garmin is really bad at handling corner cases like this. (Arguably this isn't even a corner case, as Map is a whole activity of its own.)

    It would be funny if people who were used to having touch available in the preview stage got mad if Garmin implements your suggested fix. For example, maybe some people take advantage of touch to change activity settings / data screens, but they don't want it after the activity is started.

    Paulr707 said:

    I see this has been reported before in various ways but I don't think anyone made the connection that the touch setting for an activity only works if the timer for that activity is running. e.g.

    forums.garmin.com/.../15-19-bug-touch-not-working-in-maps-if-general-use-touch-is-off

    I disagree that this bug is related tho. That bug is about the maps data screen within a "normal" activity (e.g. Run or Walk), not the Maps activity. I think what happened there is:

    1) originally the maps data screen worked just like the other activity data screens - it followed the activity touch setting

    2) some people requested that they want touch disabled for all activity screens except the map screen, so Garmin changed the map data screen behavior to follow the general use touch setting

    3) as in the bug linked above, the previous change annoyed people who have touch turned off for general use, but turned on for the activity, so they reverted to the original behavior of following the activity touch setting (1)

    The current situation is that people who liked the behavior in (2) are mad again. You really can't make this stuff up

    IMO, Garmin should've either:

    - created an explicit option to enable touch for map screen only. e.g. On Fenix and Epix watches, the activity touch settings are: off, on, and map only

    or

    - been smarter about the workaround described in (2). For example, they could've enabled touch for the map data screen if touch was enabled for *either* general use or the current activity. But sad to say, that's def not how Garmin thinks

    The crazy thing is they already have a working solution for Fenix and Epix, but for some reason they won't port it to Forerunner watches.

  • 0 over 1 year ago in reply to FlowState
    FlowState said:
    I disagree that this bug is related tho. That bug is about the maps data screen within a "normal" activity (e.g. Run or Walk), not the Maps activity

    Thanks for your detailed reply. Yes, you are of course correct. I read the title but didn't read the content properly so assumed it was the same bug. This is indeed different. For this one, I think it's probably most consistent that the touch control for map within a normal activity follows the touch setting for the activity itself - but of course best solution would be to offer "Map only" touch option as with Fenix/Epix.

    Back to the newly reported bug, it's interesting that if you try to change the touch setting within the preview screen of an activity by using the controls menu, or using a hotkey set to toggle touch, it correctly modifies the activity touch setting. But this has no effect because the touch screen at this point is following the "General use" touch setting.

    So I still think the correct fix should be to make all activities observe the touch setting for the activity while in the activity preview stage (timer not running). And yes, the fact that the touch setting for the stand-alone map activity is just wrong makes this a bug rather than a feature!