Complications questions

hi mates,

I think I am not "smart" enough or lack of skill to understand the complications,

I read the CoreTopic again and again but in vain ;)

So far I did test that:

function onPress(clickEvent){
		var c = clickEvent.getCoordinates();
		if(c[0]>gW*0.4&&c[0]<gW*0.6&&c[1]>gW*0.4&&c[1]<gW*0.6){
				Sys.println("ok");
    			var K = new Complications.Id(Complications.COMPLICATION_TYPE_SUNSET);

				if(K!=null){
					Sys.println(Complications.getComplication(K).value);
					try{
            			Complications.exitTo(K);Sys.println("exitTo OK");
						return true;
					} catch ( e ) {Sys.println("AppNotInstalled");}
				}
		}
	}

it seems to work, I mean I have the value and the "exitTo OK"

I guess the similator does not simulate the app opening right?

That is the only code block which contains Complications code.

So now my question is, what is the interrest of "suscribe" etc?

have a great day

Top Replies

All Replies

0 jim_m_58 over 2 years ago in reply to _psx_

Yes, up to 4 if I recall. There was a whole breakout about complications at GDVC 2022 - 30-45 minutes if I recall. I hope Garmin posts the video soon for folks that missed it.

"Complications aren't complicated". I do recall that also FW that supports this will come out in early 2023 though.

0 _psx_ over 2 years ago in reply to FlowState

ux costs battery... I prefer raw ux and 6 day without charging instead of 1 day

for me the biggest problem is unfixed bugs (ciq, firmware). You can build quality without ux but with bug not.

0 FlowState over 2 years ago in reply to _psx_

_psx_ said:
ux cost battery... I prefer raw ux and 6 day without charging instead of 1 day

for me the biggest problem is unfixed bugs (ciq, firmware). You can build quality without ux but with bug not.

Agreed.

My main reason for using a Garmin running watch isn't battery life (although it's a consideration), but the 5 button interface and ability to use the important sports-related functions of the watch precisely and without looking (start, pause/resume and lap).

The bugs drive me crazy though. And one example of how a bug / bad UX ruins a feature is how map panning is stuck / extremely slow on 945 LTE. It means that the mapping feature is almost useless to me if I want to do something simple like explore the area around me. A button-based interface doesn't have to be bad (look at video games), but with Garmin, it often is. Look at Spotify UX on Garmin vs Apple - so many bugs and missing features on Garmin (you can't even select a specific track to play, you have to select a whole playlist)

So if someone asks me "what are main advantages of Garmin over Apple watch" (or Android or some other running watch), I could say "offline mapping :D", but then I'd have to add "but it's broken on my watch :(".

0 _psx_ over 2 years ago in reply to jim_m_58

unfortunately I have chosen other subject and was late.

0 jim_m_58 over 2 years ago in reply to _psx_

I don't think the battery cost will be that high. With some devices, some native watch faces have supported this for a while, but only with native stuff., Also understand that things like the f7 have a very long battery life.

0 _psx_ over 2 years ago in reply to FlowState

Honestly speaking I have changed gear Samsung to f6p due to problem with gps and for spo2.

And after few updates of firmware both are very bad on my f6.

Yes, offline maps was useful in few cases but only to not stop running or biking (I have never been out off mobile network so could use e.g. Google maps).

now using my own apps is the most important, I have data I need, a lot of data :-)

0 _psx_ over 2 years ago in reply to jim_m_58

on condition you don't use gps and spo2 and hr and... all sensors

in this case I prefer my automatic Longines - it never stops if I wear it everyday:-)

0 FlowState over 2 years ago in reply to jim_m_58

_psx_ said:
ux costs battery... I prefer raw ux and 6 day without charging instead of 1 day

jim_m_58 said:
I don't think the battery cost will be that high. With some devices, some native watch faces have supported this for a while, but only with native stuff., Also understand that things like the f7 have a very long battery life.

_psx_ means the battery cost of the Apple Watch's beautiful UI/UX, not the battery cost of complications.

0 _psx_ over 2 years ago in reply to FlowState

to clarify, battery consumption

and I use Garmin pay often but it's impossible to add card to door so still have to use plastic :-(

Garmin please add functionality to scan and store any nfc card to allow people leave they plastic card in pocket :-) Unfortunately I've tried to adopt something but watch sends numbers that are randomised.

0 Shent-Aurkhan (SHN) over 2 years ago

hi everyone,

so my F6SS has been updated with 11.25 (System6 compatibility)

I sideloaded so a PRG to do some test,

the onPress works like a charm!!! so good!

But I can't make the touch/opening app at all...

when I do test on the simulator, everything seems to work, I have a "xxx launched" but on on real device,

I have "IQ" logo,did I miss something?

here is how I do it:

if(wD!=null&&wD>0){
			wD=whichComp(wD);
			if(wD==null){return false;}
			try {Comp.exitTo(new Comp.Id(wD));}
			catch (e){return false;}
		}

the whichComp function return a number according the Complication module (1=battery etc)

have a great day