Watchface: M2

Perfect app, thank you. First try .. F6x

One here from @B__S : https://forums.garmin.com/developer/connect-iq/f/showcase/217072/sec-alti-bat-clock-next-sun-event-next-dawn-dusk-event-date

01Ys2552211WDPO1011WwWO023Vc13QIVe21Vc51WwP035C13SC13BC13SC11XGXj13VaCO3UHO1WEVs03VjC13QC13VkC11WDXj03VvC14VW011WwYC03W1CVf1XiVs03WkC13QC13WlC1

Amazing watchface. Great work, Mark!

Here's my setup:

01Ys5225111WDPO1011WwY40b0S01bGS013WN713Q713Vk711WwXb03X7713N7135713N713XD711WwWO023VW121U11WwVw03Vd714R0Vw3N713VV714L011WwR0WMC11VqVV11XeO1VwZCI1VwZSG1VwWsF1183B0VxVw0383F0VxVw038050Vx5008N40Vx100PF10000

At the bottom, icons for alarm, move alert, low battey, phone not connected, do not disturb, and pending notifications appear according to the watch status.

The red ring shows the battery level and the black seconds ring indicator shows the move bar.

The black seconds indicator only appears on gesture.

HI nice one...can you help me change UTC with steps ?? 

That's a cool one! Already enjoying it on my watch. Thanks for sharing!

Hello Mark,

first of all - thank you very much for your great work, this watch face brings my experience with my Garmin watch to another level

here is my design:

base screen is pretty simple based on one of previous ones here from this thread. Steps icon goes red when move alert is raised and also battery icon goes red when battery is low.

watch face turns into this when gesture is active:

small numbers under minutes are day and week numbers

here is code, 

part1:

01ZC2525111WDPO2011X6WX020Vd121VaEHX6Vn04R013VeC13NC14I013VaC13UC11X6N0WrVZF1WsF01WMC01XOE01VqVV01YQH01YQVX01ZCH0VdZCVX0VdVXX6Y90ZiL01ZSL0Vw3NC13VVC1PB50000HX6YE04Q013NC13VmC1HYpWH238313T313N313E31HVfXr14S013Vf313Q313Vg31HYXXr24T013Vh313Q313Vi31HMWG13X721

part2:

VXX6Vs036C13NC13XDC1HX6Yk04VW013Vv31

______________________________________

A couple of times you asked about editing on touch screens: I think it is fine, the only little annoying thing is when you changing position of the field you need to swipe down or up for single pixel movement. So if you need to change position over 50 pixels you need to swipe 50 times. I am not sure, but I suppose when you are using buttons for movement, you can hold it for bigger movement. Anyway, it is just a little detail, everything works fine on touch screen device

 1906207

Nice one, and thanks for posting 

And the feedback on the touchscreen usage is helpful - at least it is working . And yes … swiping 50 times … does not sound that ideal! In fact people with buttons have to press the button … 50 times … also not that ideal!!

For pressing and holding the button I can't think of a better way to do it yet, since long button presses tend to be used for other system things.

For the touchscreens it "may" be possible to add an option to tap on the screen for where you want to position something - but I haven't tried to implement this yet. Maybe a tap on the screen for a rough location, and then lots of swipes after that (only 25 or so …) to get the exact position. It is on my list to try this at some point (in the simulator). Or it may be possible to test the length of the swipe and move 2 pixels (a whole 2 pixels!!!) for longer swipes - but I think the tap might work better.

I got your point, but I can imagine implementing would be quite difficult and I think it is not worth the time.

Maybe suggestion: much easier would be to implement new method for moving objects over, for example 10 pixels with single swipe / button press. So under position menu there would be 2 methods for moving over single axis. One would be same as current and second would be to move over more pixels - so when I would like to move a field over whole display, I would choose the second method to get near the target and then the first method for final adjustment

1906207 Aha that is a great suggestion, thanks! I'll definitely add this in. Plus it will work for buttons too. In theory, maybe 16 is about the optimum value since 16*16=256 and the screens vary in size from 218 to 280.