[Question] No stupid questions - ask anything here

Raimo Järvi

@Thibault-B. said in [Question] No stupid questions - ask anything here:

Can we get current ZoneSense zone information? I have not found the key of such data.

It’s not mentioned in documentation, but editor’s autocomplete shows there’s /Fusion/Ddfa input resource. I’m not sure how that value maps to zones.

I struggle to make the “PREV INT” data slightly bigger (not as big as current rest/int data - which is sp-d-s -).
“PREV INT” data is currently sp-d-xs for which I tried to override font size, rescale. Note that on simulator it might looks fine but not on the watch (can be bigger but then uses a default font which includes big spaces between numbers, etc).

Watch has only a predefined set of font sizes (unless there’s been some improvements to font support). For numbers you should use one of the sp-d- CSS classes, those already cover the available font sizes.

Documentation has this somewhat vague sentence: “The older watches do not support every possible font size and thus using the css classes for font sizes (shown below) can generally lead to less errors.” This hints that there might be better font support in some watches, but I don’t know what “older watches” means here. In any case, if you want to support all watches, you’re probably limited to sp-d- classes.

Thibault B.

@Raimo-Järvi
Thanks for your answer!

I hadn’t thought about exploring the autocomplete suggestions—great idea! It works really well. I mapped values to zones based on what I’ve observed in my previous activities using ZoneSense.
OK. Then, personally, I really miss an intermediate size between sp-d-xs and sp-d-s
You seem to confirm that there’s no way to slightly increase the size (I was about to experiment with canvas…). Easily supporting all watches wasn’t my main concern anyway—I would have been fine defining this intermediate font size per watch model if needed.
Regarding older watches: does it still make sense to support watches older than the Suunto 9 Peak Pro, or is the information in the documentation confirmed?
“Note: SuuntoPlus is no longer maintained for UI1 (s, m, l).”
Does this mean that my app simply cannot be installed on those watches?

AYamshanov

@brechtvb I had an option to switch my device to NO_PIN mode and I followed this approach to continue development and do not stuck ¯(ツ)/¯

Raimo Järvi

@Thibault-B. said in [Question] No stupid questions - ask anything here:

Regarding older watches: does it still make sense to support watches older than the Suunto 9 Peak Pro, or is the information in the documentation confirmed?
“Note: SuuntoPlus is no longer maintained for UI1 (s, m, l).”
Does this mean that my app simply cannot be installed on those watches?

Information in documentation is a bit vague again, but I think it’s trying to say that UI1 watches don’t get any updates to SuuntoPlus features. If you don’t use any SuuntoPlus features that have been added to UI2 watches (e.g. settings), I think apps should still work in UI1 watches. Older watches also have less JavaScript memory, that’s another potential cause for app incompatibility. But since I’m not aware of the latest SuuntoPlus developments, I may be interpreting the documentation incorrectly.

Thibault B.

@Raimo-Järvi Make sense thanks.

Other question: how to make a pop-up like the multi-sport one when long pressing a button (progress ring, etc)? I saw the reference in documentation regarding the lock pop-up but it also lock the button which is not what I want. I want to use such pop-up as toggle for an option.
@suuntopartnerteam can you provide support on that? Thank you.

Raimo Järvi

@Thibault-B. You can catch long press with onLongPress in pushButton element. And maybe Popup example in SuuntoPlus editor could work for toggling an option. But I don’t know how to get the progress ring. I don’t know if it’s part of the multi-sport popup, or if it’s generic functionality that can also be used elsewhere. In theory, you could catch onLongPressStart and implement your own progress ring view, but that would probably be difficult to implement.

surfboomerang

Can a CSS guru help me out?

I want to show the current speed in the center of the screen. This works fine without a postfix, but as soon as I add a postfix, the speed fields shifts slightly to the left because both <span> elements are centered together.

How do I center the first <span> element and put the postfix right of it?

    <div class="sp-d-s p-hc" style="top:calc(87% - 50%e)">
      <span>
        <eval input="/Activity/Current/Speed" outputFormat="{zapp_speed_format}" default="--" />
      </span>
      <span class="cm-mid sp-t-s" style="padding-top:6px; padding-left:4px">
        <postfix />
      </span>
    </div>

Timo Helfer

Hey guys, could someone make HRV reading work?

I do not get the values, even tough the Suunto Smart Belt is conencted.

In the SImulator it says “undefined” for /HrvRmssd

bhamp0

Hi guys!
Is there any solution to get the NGP values?
I tried two different syntaxes: /Activity/Move/-1/NormalizedGradedPace/Current and /Activity/Move/-1/NGP/Current but both are unrecognized.
Thanks a lot

bhamp0

(duplicate)