I have SaO2 set in the bottom right but it always says 96% even if I hold my breath for long enough to dip it. Does it require any other setting to function?
I have SaO2 set in the bottom right but it always says 96% even if I hold my breath for long enough to dip it. Does it require any other setting to function?
If anyone from Garmin is reading this, the reason this happens over and over again is when you click on the “Latest” (reply in thread) link in the topic list, it takes you to the latest post for that thread *and* it shows the “+ New” button on the top right-hand corner of the page.
The "+ New” button will create a new thread/topic, but what’s happening here is obviously people think that “+ New” will create a new reply in the existing thread, and I don’t blame them.
This was partially fixed in the past by removing the "+ New” button when clicking on the thread title in the topic list, which takes you to the first post for that thread.
I think the full fix would be to remove the "+ New” button in all cases when you are looking at a thread including:
- when you view the first post (already done)
- when you view the latest post (not done)
- when you view any post within the thread except the first post (not done)
Example using the “Watchface: Glance” thread in this forum.
- first post link [https://forums.garmin.com/developer/connect-iq/f/showcase/279043/watchface-glance] (note the lack of the “+ New” button)
- latest post link: [ https://forums.garmin.com/developer/connect-iq/f/showcase/279043/watchface-glance/1712526#1712526] (note the "+ New” button)
- link to 2nd post: [https://forums.garmin.com/developer/connect-iq/f/showcase/279043/watchface-glance/1339802#1339802] (note the “+ New” button)
Screenshot for latest post link:
You want to post in the thread for the app you are talking about.
You (and others) always reply in this exact way when this happens, but you never stop to ponder why this happens over and over again, even with people who have been on these forums for years.
Surely it must be user error every single time, as opposed to a known UI/UX issue in the forums (which Garmin has half-fixed in the past.)