Suunto Plus - bug when selecting suunto plus

[Łukasz Szmigiel]

@surfboomerang hm but it doesn’t work like that everywhere I think? Ie. when setting custom battery modes there’s no way to back-accept it, you have to accept it with top or middle I think?

[Tomas5]

@łukasz-szmigiel back button works as expected on Battery Mode, but doesn’t work on Suunto Plus, Theme and maybe others too.

In this two example back button works same way as accept button. It is strange and not intuitive behavior.

From programmers point of view it looks like some settings change inner variable while browsing list of options and other settings change inner variable when accept button is pressed.

[isazi]

I asked if this is intended or not. Not sure I’ll get an answer, but I will report if I do.

[Łukasz Szmigiel]

@tomas5 I wonder how it’s done in S9 where there’s no back button but swipe only?

[surfboomerang]

@łukasz-szmigiel True, but for settings within “custom battery mode” it does work. Try GPS setting for example

[surfboomerang]

@łukasz-szmigiel Long press middle button is the back button

[isazi]

So this is known, and expected to work this way.

[DF130]

@łukasz-szmigiel I think there is some inconsistency with the S9 as well. A little triangle at the rhs usually means one can swipe or press the middle button (eg when going through the sports modes), but when in the Suunto+ menu one can only press the right button (which then returns) or swipe in the other direction to activate one‘s choice of Suunto+, despite the little triangle being shown. Not a big deal for me but I noticed recently (mainly using Ghost)…

[herlas]

on my S9P scrolling through the list of S+ options and doing a swipe left on the screen, will leave that option as selected, not sure if we want that, also not sure if that was the behavior on S9B

[Tomas5]

@isazi sound like programmers wanted to make their job easier

[Dimitrios Kanellopoulos]

@tomas5 or UX. Else it would be a bug.

Devs only do what UX instructs.

So PO - makes feature
UX - decides how it works
Dev be like : Ooookey

[Tomas5]

@dimitrios-kanellopoulos agree

[Dimitrios Kanellopoulos]

@tomas5 it has been discussed and my self I do find it not expected as of behavior. Forward should confirm and back should cancel without applying.

But the case is that if you notice that this is inconsistent in the watch ecosystem.

Sometimes it works as expected and some options like you mention doesn’t .

I pass this and raise it once more to the UX and team.