The gesture doesn't switch the light on

Similarly, there is a setting called Health & Wellness > Goal Alerts - its options are Off, On, and Not During Activity. If you set this option to Not During Activity, and you reach your step goal while you're recording an activity, but you're looking at a watchface, glance or system settings, do you expect the goal alert to be displayed?

I expect it not to be displayed, based on my understanding of what "during activity" means. I'm curious what you would expect.

You never answered my question. If you think "during activity" has a certain meaning (i.e. "when an activity screen is visible") then you should stick to that meaning in most or all cases. What do you think Health & Wellness > Goal Alerts > Not During Activity should mean? "Not while an activity is being recorded" (my interpretation and Garmin's interpretation) or "Not while an activity screen is visible" (your interpretation). If I using the "goal alerts > not during activity" setting I certainly wouldn't want to get a goal alert during an activity just because I happened to be looking at the watchface or a glance.

It's simply illogical and inconsistent...

Gesture = ONLY light on.

If the gesture is ONLY used to turn on the light, why is it possible to turn on the light with the button?
So e.g I start tactic activity and I don't want any light but settings give me the ability to prevent accidental switching on of the light by gesture but not y accidental pressing of the button...

This is the 3rd issue you have raised here, in addition to the other 2, unless I missed it before.

"If the gesture is ONLY used to turn on the light, why is it possible to turn on the light with the button? "

Like I said, this doesn't really make any sense.

---

So here's the 3 separate, yet kind of related issues I see in this bug report:

1) On Fenix 7, Connect IQ device apps (e.g. PSX-7) use the Display > During Activity settings even though no activity is recorded. In the same situation, native glances use Display > General Use settings, as expected.

I agree with this one.

2) When switching to a watchface during an activity, you think that the watchface should use Display > General Use settings, but in fact the watch uses Display > During Activity settings.

Like I said, I strongly disagree with this. It's very consistent behaviour, and it makes sense. "During Activity" means "while an activity is active/happening/being recorded", and nothing about "During Activity" suggests that an activity screen has to be visible. If I return to the watchface during an activity, I know that the activity is still being recorded in the background.

3) Garmin should allow the Light button to be disabled

To me this is a completely different feature request. It's perfectly fine (I would vote for it), but I disagree that it's illogical or inconsistent that Garmin doesn't already have this feature. The gesture is not the same as the Light button (see below).

settings give me the ability to prevent accidental switching on of the light by gesture but not y accidental pressing of the button...

First of all, it's a lot easier to accidentally do the gesture than it is to accidentally press the Light button.

Second, you usually have to purposely do do the gesture just to look at the watch (unless you just glance down and your arm is at the correct angle), so it makes a lot of sense that Garmin has an option to prevent the light from turning on when you do the gesture. Otherwise there would be a huge battery impact from the people doing the gesture all day, just to look at their watch.

On the other hand, you don't have to press the Light button to look at the watch, not to state the obvious. And if you do press the Light button by accident, it's usually not going to happen that often, so it's not the end of the world that the light always turns on. It certainly won't have a large battery life impact (unless you have a MIP device, you configure the backlight to have no timeout, and you don't notice the backlight is on, maybe because it's daytime). But ofc that would require you to purposely change the backlight timeout setting.

Similarly, there is a setting called Health & Wellness > Goal Alerts - its options are Off, On, and Not During Activity. If you set this option to Not During Activity, and you reach your step goal while you're recording an activity, but you're looking at a watchface, glance or system settings, do you expect the goal alert to be displayed?

I expect it not to be displayed, based on my understanding of what "during activity" means. I'm curious what you would expect.

You never answered my question. If you think "during activity" has a certain meaning (i.e. "when an activity screen is visible") then you should stick to that meaning in most or all cases. What do you think Health & Wellness > Goal Alerts > Not During Activity should mean? "Not while an activity is being recorded" (my interpretation and Garmin's interpretation) or "Not while an activity screen is visible" (your interpretation). If I using the "goal alerts > not during activity" setting I certainly wouldn't want to get a goal alert during an activity just because I happened to be looking at the watchface or a glance.

It's simply illogical and inconsistent...

Gesture = ONLY light on.

If the gesture is ONLY used to turn on the light, why is it possible to turn on the light with the button?
So e.g I start tactic activity and I don't want any light but settings give me the ability to prevent accidental switching on of the light by gesture but not y accidental pressing of the button...

This is the 3rd issue you have raised here, in addition to the other 2, unless I missed it before.

"If the gesture is ONLY used to turn on the light, why is it possible to turn on the light with the button? "

Like I said, this doesn't really make any sense.

---

So here's the 3 separate, yet kind of related issues I see in this bug report:

1) On Fenix 7, Connect IQ device apps (e.g. PSX-7) use the Display > During Activity settings even though no activity is recorded. In the same situation, native glances use Display > General Use settings, as expected.

I agree with this one.

2) When switching to a watchface during an activity, you think that the watchface should use Display > General Use settings, but in fact the watch uses Display > During Activity settings.

Like I said, I strongly disagree with this. It's very consistent behaviour, and it makes sense. "During Activity" means "while an activity is active/happening/being recorded", and nothing about "During Activity" suggests that an activity screen has to be visible. If I return to the watchface during an activity, I know that the activity is still being recorded in the background.

3) Garmin should allow the Light button to be disabled

To me this is a completely different feature request. It's perfectly fine (I would vote for it), but I disagree that it's illogical or inconsistent that Garmin doesn't already have this feature. The gesture is not the same as the Light button (see below).

settings give me the ability to prevent accidental switching on of the light by gesture but not y accidental pressing of the button...

First of all, it's a lot easier to accidentally do the gesture than it is to accidentally press the Light button.

Second, you usually have to purposely do do the gesture just to look at the watch (unless you just glance down and your arm is at the correct angle), so it makes a lot of sense that Garmin has an option to prevent the light from turning on when you do the gesture. Otherwise there would be a huge battery impact from the people doing the gesture all day, just to look at their watch.

On the other hand, you don't have to press the Light button to look at the watch, not to state the obvious. And if you do press the Light button by accident, it's usually not going to happen that often, so it's not the end of the world that the light always turns on. It certainly won't have a large battery life impact (unless you have a MIP device, you configure the backlight to have no timeout, and you don't notice the backlight is on, maybe because it's daytime). But ofc that would require you to purposely change the backlight timeout setting.