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 FlowState 5 months ago in reply to peterdedecker

I suspect the limitation has to do with the fact that they can not handle the launching aspect of the complication.

That could be part of it but I think the overall reason is that complications are only meant for watchfaces, by design. It's in the name of feature itself: "complication" is a traditional watchmaker term for data that appears on a watchface other than the time. Remember how ppl complained that complication is a dumb term when the feature was first announced? Well, I'm pretty sure it was chosen deliberately. I bet one of the reasons is that Apple also uses the term complication for the corresponding feature on Apple Watch. I think another reason is that it's meant to refer to data that appears on a watchface.

I know it sounds overly simplistic, circular, and "just so", but I think it's really that simple.

I agree it would be nice compromise if the data sharing aspect was available in all app types.

I agree with this too. There's *probably* no technical reason it couldn't have been done this way from the start (at least for native complications), so I'll go back to my previous assertion that it was intentionally limited to watchfaces simply bc it's a feature that's only meant for watchfaces (even if other app types could benefit from it as well.) Perhaps it was even designed or implemented in such a way that only watchfaces can (easily) access that data, who knows.