The gesture doesn't switch the light on

> You don't have to persuade me to your point of view. 

You're right, I don't. I did spend a lot of time and effort trying to test your bug for you and trying to figure out / explain why I think it works that way.

But don't be surprised if Garmin never changes this behaviour. I just tried to explain why I think things are the way they are, and you're refusing to even consider a different POV, which is fine. Doesn't matter how much evidence or logic I provide, which is ok. Actually not the first time it's happened.

My POV happens to correspond the reality of how the watch works, so there is that. Your POV revolves around some functionality that you wish to have but doesn't actually exist (ability to turn off gesture for activity screens, but leave gesture on when viewing a non-activity screen during an activity).

I even suggested some settings which could fulfill your use case (Keys & Touch = On, Gesture = Off) -- assuming I understand your use case -- but you ignored that, which is cool. I really don't understand why those settings wouldn't work for you, since in order to view a non-activity screen, you have to use keys/touch, which means the light would come on in that case.

And your arguments really don't address your actual complaint in this bug report. e.g.  you said: if light is so important, why is there a setting to turn off the gesture but not the light button? You realize that Garmin could add a setting to turn off the light button, and it still wouldn't address the complaint of this bug report, right?

I also don't get where "if light is so important" is coming from, in the context of this bug report and discussion. Garmin's current implementation of display settings doesn't imply that they think light (control) is more important than you do. As a matter of fact it seems you want more finer-grained control of light than Garmin currently provides, so maybe light is even more important to you than it is to Garmin.

If I'm right, this functionality has always worked this way, and it's intentional, which means it's very unlikely Garmin would change it because you see things differently. If they changed how "During Activity" works, that would also run the risk of annoying other people who like it the way it is. If they add more granular settings (idk "During Activity (foreground)" and "During Activity (background)"), that might give you what you want, but it would add more complexity for Garmin and its users.

> Nobody knows what was the cause to add such functionality so it's not impossible to know if it's implemented for or notrequirement.

Garmin probably knows why it works the way it does. The real question is whether they will bother explaining it to us in black and white. I don't think Garmin even understands the complaint you are making tbh.

And I think it's fairly obvious why the general Display mode functionality was added. The idea is that the user wants different behaviour for the backlight during an activity, during sleep and in all other cases (general use).

- During Sleep: obviously users want to pay less attention (or no attention) to their watch while they are sleeping, so it makes sense to disable the gesture (for example) in this mode

- During Activity: I can't speak for you or anyone else, but when I am doing an activity, I pay *more* attention to my watch than at other times, so in this case (for me personally only), I turn off the gesture timeout and set the gesture to "after sunset", so that when there's no sunlight, the backlight stays on for the whole activity after the 1st time I turn it on.

- General Use: Again I can't speak for you, but I pay less attention to my watch when I'm not in an activity, so in this case I use a normal timeout for the gesture (which is also set to "after sunset").

Seems pretty simple to me, and it seems that the behaviour you want is more complex. Let's say Garmin is convinced by your arguments and decides that "during activity" should only mean "when activity is in foreground" or "when I am looking at an activity screen".

- Does activity settings count as "during activity"? How about system settings?

- how about the music player?

- what about people who have the gesture enabled during activity but disabled for general use (the opposite of what you have, if I understand your use case correctly)? If Garmin does things the way you want, they will be very annoyed because they will have the opposite problem as you: when they go back to watchface during an activity, the gesture won't work even though they have it enabled for During Activity.

I still don't understand why you think it's such a mystery that settings in a menu called "During Activity" will apply during an activity and/or why you think that when you switch to another screen during an activity it necessarily no longer counts as "during an activity".

I might agree with you if it was a general purpose device like Apple Watch or iPhone, but for a watch where the core functionality revolves around timed activities, this implementation makes sense to me.

> You don't have to persuade me to your point of view. 

You're right, I don't. I did spend a lot of time and effort trying to test your bug for you and trying to figure out / explain why I think it works that way.

But don't be surprised if Garmin never changes this behaviour. I just tried to explain why I think things are the way they are, and you're refusing to even consider a different POV, which is fine. Doesn't matter how much evidence or logic I provide, which is ok. Actually not the first time it's happened.

My POV happens to correspond the reality of how the watch works, so there is that. Your POV revolves around some functionality that you wish to have but doesn't actually exist (ability to turn off gesture for activity screens, but leave gesture on when viewing a non-activity screen during an activity).

I even suggested some settings which could fulfill your use case (Keys & Touch = On, Gesture = Off) -- assuming I understand your use case -- but you ignored that, which is cool. I really don't understand why those settings wouldn't work for you, since in order to view a non-activity screen, you have to use keys/touch, which means the light would come on in that case.

And your arguments really don't address your actual complaint in this bug report. e.g.  you said: if light is so important, why is there a setting to turn off the gesture but not the light button? You realize that Garmin could add a setting to turn off the light button, and it still wouldn't address the complaint of this bug report, right?

I also don't get where "if light is so important" is coming from, in the context of this bug report and discussion. Garmin's current implementation of display settings doesn't imply that they think light (control) is more important than you do. As a matter of fact it seems you want more finer-grained control of light than Garmin currently provides, so maybe light is even more important to you than it is to Garmin.

If I'm right, this functionality has always worked this way, and it's intentional, which means it's very unlikely Garmin would change it because you see things differently. If they changed how "During Activity" works, that would also run the risk of annoying other people who like it the way it is. If they add more granular settings (idk "During Activity (foreground)" and "During Activity (background)"), that might give you what you want, but it would add more complexity for Garmin and its users.

> Nobody knows what was the cause to add such functionality so it's not impossible to know if it's implemented for or notrequirement.

Garmin probably knows why it works the way it does. The real question is whether they will bother explaining it to us in black and white. I don't think Garmin even understands the complaint you are making tbh.

And I think it's fairly obvious why the general Display mode functionality was added. The idea is that the user wants different behaviour for the backlight during an activity, during sleep and in all other cases (general use).

- During Sleep: obviously users want to pay less attention (or no attention) to their watch while they are sleeping, so it makes sense to disable the gesture (for example) in this mode

- During Activity: I can't speak for you or anyone else, but when I am doing an activity, I pay *more* attention to my watch than at other times, so in this case (for me personally only), I turn off the gesture timeout and set the gesture to "after sunset", so that when there's no sunlight, the backlight stays on for the whole activity after the 1st time I turn it on.

- General Use: Again I can't speak for you, but I pay less attention to my watch when I'm not in an activity, so in this case I use a normal timeout for the gesture (which is also set to "after sunset").

Seems pretty simple to me, and it seems that the behaviour you want is more complex. Let's say Garmin is convinced by your arguments and decides that "during activity" should only mean "when activity is in foreground" or "when I am looking at an activity screen".

- Does activity settings count as "during activity"? How about system settings?

- how about the music player?

- what about people who have the gesture enabled during activity but disabled for general use (the opposite of what you have, if I understand your use case correctly)? If Garmin does things the way you want, they will be very annoyed because they will have the opposite problem as you: when they go back to watchface during an activity, the gesture won't work even though they have it enabled for During Activity.

I still don't understand why you think it's such a mystery that settings in a menu called "During Activity" will apply during an activity and/or why you think that when you switch to another screen during an activity it necessarily no longer counts as "during an activity".

I might agree with you if it was a general purpose device like Apple Watch or iPhone, but for a watch where the core functionality revolves around timed activities, this implementation makes sense to me.