Salve a tutti. Mi ritrovo un problema: Non riesco a far funzionare una bussola e non ho neanche la più pallida idea di come si comincia. Uso il tag della bussola ma poi??? Qualcuno gentilmente può indirizzarmi sull’operazione?
First of all you watch has to have the compass sensor, which I hope it has…
Then add a compass element and add the rotation: (#-CMP#)
You can find some compass hands, needles here:
Grazie tom.vannes. La bussola dovrei averla nel Ticwatch Smartwatch Pro 3 LTE. Non c’era nel PRO 3, ma nel PRO 3 LTE so che c’è, anche se non la ho mai usata. Del resto c’è anche maps. Provo questa tua formula. Ho scaricato le lancette, aghi e bussole per quando riuscirò a farla partire. Grazie ancora amico.
Tom (-#CMP#)
is NOP . -(#CMP)
is a worker . For rotating the Dial of the Compass .
This is the correct expression in my eyes.
-(#CMP#)
does work but I have no idea why as it breaks the rules of keeping calculated expressions inside brackets. Logically it is equivalent to 0-(#CMP#)
which does not work at all where (0-#CMP#)
does.
I have always used (-#CMP#)
for a rotating bezel compass.
Thanks . I will not corect it but stand corrected . Many just put - outside to invert the rotaton . Should it not Technicaly be (360-(#CMP#)) . We are just lucky that creator handles large numbers under zero .
There is zero point in putting brackets around a single tag so if you mathematically optimise (360-(#CMP#))
it becomes (360-#CMP#)
. You would not write (360-(30)).
I also find that unnecessary brackets makes the matching, and reading at a glance, all the harder.
As a static point 0 and 360 are interchangeable in the expression as are 270 and -90 etc. The first can be seen either end of the designer slider. It is only the sign before the tag that determines direction of motion.
I don’t believe the answer is quite so simple afterall we are dealing with rotary motion where a minus sign is not necessarily mathematic indicator of subtraction but can also be a simple indicator of direction clockwise or anticlockwise.
I also disagree that the use of parentheses can be a problem - i was taught to use them to ensure the order of operators is clear to those reading the calculation in the same way that i was not allowed to do calculations in my head to arrive at an answer- it was necessary to show how i arrived at the answer.
I agree to the extent of separating parts of a calculation. It’s overuse and unnecessary ones I find a problem. (2*3-4)
will always be calculated by a language as 2 because order of precedence says so but I would not be overly upset by ((2*3)-4))
. I would be aghast to see (((2)*(3))-(4)))
however.
Ha Ha . Yes and yes . Sadly in some Syntax we have to put Variables into Parenthesis to force them to be Integers . Otherwise they are strings. We need a good strong topic on Natural Precedence of Operands . Sadly my Brain will not let me Learn it . So I use the KinderGarten Mode .