This would allow easy sharing and re-use of favourite formulae (moon-phase, animation, etc.), with the ability to change, swap, or update the code without needing to edit the display portion of the watchface.Ī ‘black box’ software engine, embedded in Facer (Creator, and on watch runtime) This is NOT specific to date/time, and would still need additional timezone and UTC tags or functions.ĭesign discussed here: Forumlae ONLY page, alongside (current) WYSIWYG view Non-displaying formulae fields, with user variables for using the output in their watchface design (or as input to other formulae). This could be extend to forcing PST (or PDT), or other timezones - for showing dual timezones or many timezones. This is needed for displaying both or complex fields/dials that are calculated during/over the daylight/standard transition. The root tags ( #DUH#, #DUm#, and #DUs#) are still needed for calculations.Īlso useful would be: &timezone:daylight& to force daylight time, and &timezone:standard& to force standard time. &timezone:UTC& (or short form: &tz:UTC&), and then removing all the existing (presentation) UTC specific tags. Note: Using an expression like $#DH#-#DUH#<0? (#DD#-1) : #DD# $ is problematic for all possible local timezones.Ī more elegant solution would be support for ‘pragma’ prefixes (eg. for AEST (Australia, Eastern Standard): +10 hours, +0 minutes for PDT (US, Pacific Daylight): -7 hours, -0 minutes The minimum requirement is 2 new tags: #DUD# and #DUd# - which would provide the correct day-in-year and day-in-month UTC values for date calculations.Īnd 2 new tags (? #diffDH# and #diffDm#) for hour- and minute-difference to support timezone calculations. This has some unintended consequences, and is difficult ( if not impossible) to rectify with conditional logic. There are no equivalent tags for some forms, and none for UTC Year, Month or Day (of month, or year). Nine are for hour, and two each for minutes and seconds. Currently there are 13 tags for UTC date/time.
0 Comments
Leave a Reply. |