[Question] No stupid questions - ask anything here

Thibault B.

I’m having trouble getting this to work on my device . I then found this comment to see if I can figure it out but no.
It works fine in the simulator, but not on my Suunto Race S.

Here’s the relevant part of my code:
<uiViewSet id=“prevIntSet” onTap=“$.put(‘/Zapp/{zapp_index}/Event’, 2, null, ‘int32’)”>

In my JavaScript, I handle event ID 2 and update a variable that switches between different uiViewSet views. However, it seems like the tap interaction isn’t triggering anything on the watch.

I also checked the settings on my Race S but couldn’t find anything that might be blocking this behavior.
One thing I noticed: when the screen dims, tapping doesn’t seem to do anything at all—except on the map screen, where it wakes the display. This makes me wonder if there’s a setting or limitation that completely disables tap events in a SuuntoPlus app.

Has anyone encountered this or knows if there’s a specific setting I might be missing?

Thanks in advance!

SuuntoPartnerTeam

@surfboomerang No comment on getting the runtime token working outside of <eval>, but in case it’s of any help, an alternative, more standard solution might be:

function getUserInterface() {
  output.index = ??? // here or somewhere else'
  return { 
    template: "t"
   };
}

and

<uiView onLoad="
  function change(idx) {
    navigate('#uiViewSet1', idx)
  }
  $.get('Zapp/{zapp_index}/Output/index', change);
">

SuuntoPartnerTeam

@Thibault-B. Are you absolutely sure you have touch enabled? Sounds like you are doing an exercise which has the touch options ‘Map Only’, ‘On’ or ‘Off’ and yours is on ‘Map Only’. You can switch it to ‘On’ either via ‘Exercise options’ before starting the exercise or by holding the down button during the exercise to open the control panel.

And just for clarity, this works on the original Race:

<uiViewSet id="uiViewSet1" onTap="$.put('/Zapp/{zapp_index}/Event', 2, null, 'int32')"
     style="top: 50%; left: 50%; width: 150px; height: 150px; background-color: red;">
      <div>lol</div>
      <div>lel</div>
    </uiViewSet>

function onEvent(_inp, _out, event) {
  if (event == 2) {
    next("#uiViewSet1", event);
  }
}

As an aside, this is also why using touch events is a bit problematic, since they often aren’t ‘On’ for many watch users.

Unpaired8373

@suuntopartnerteam I am working with a sprite map currently and have two approaches where I would need some guidance on:

Is it better to have a bigger sprite map with different permutations of individual elements or is it better to have a smaller map with each element as individual sprite but more <img> tags in the HTML?

Thibault B.

@SuuntoPartnerTeam Thanks for your reply.

I tested your code in a fresh default project created from scratch. It works correctly in the simulator, but still not on my Suunto Race S.

I also reviewed the watch settings. The only options that seem potentially related to the touchscreen are “Do Not Disturb” and display settings (AOD, full wake-up), and both are configured correctly.

In my case, the touch event is not critical—it’s mainly a nice-to-have feature used to manually cycle through data, which already rotates automatically every few seconds.

Raimo Järvi

@surfboomerang said in [Question] No stupid questions - ask anything here:

I’m trying to pass the default index of a uiViewSet like this:

main.js
function getUserInterface(input) {
  return { 
    template: "t",
    uiViewSet:{index: input}
   };
}

This is assigning all input resource values (i.e an array) to index, perhaps that’s not what you’re looking for? You could use an individual input or output value, e.g.:

function getUserInterface(_input, output) {
  return { 
    template: "t",
    uiViewSet: { index: output.index }
  };
}

There also seems to be some string case conversion going on, I only get it to work if I use all lowercase {zapp_uiviewset_index} in HTML.

Perhaps the more standard solution in the previous answer is better, but using input or output values is also possible.

Also, if you return uiViewSet:{index: input}, the minified JavaScript code will be: return{template:'t',uiViewSet:{index:input}}. This seems incorrect, because input variable doesn’t exist in the minified code. Maybe there’s no use case for this, but looks like a JavaScript conversion / minifier bug anyway.

surfboomerang

@Raimo-Järvi Nice find! Thanks for diving into this as well.
In the mean time I had to change some other code and the issue became obsolete, but I will definitly remember this in future projects.

chus1962

Hi.

Is there a way to obtain the GPS position using a input resource other than

/Navigation/Gps/Coordinates/{Filter}

which requires enabling navigation on the watch at the start of the exercise, something that’s not desirable for the app I’m developing?

Thanks.

assaf1007

@Tomas5 the only diff is see between us is the stroke color. maybe default is black so you don’t see it?

assaf1007

2 questions regarding Settings

How can a user approach my app’s seetings if i bypass the suuntoplus app? (i deploy directly…)
and another settings question:

on vsCode i wish to keep a setting value for the next time, so , as a test to see if it works i do:

so i’m advancing ++ and saving.

on vsCode indeed it works (i added debug on UI to view value), but on my watch it stays 1…
ideas?