Watchmaker Wiki

The ultimate watch maker for Android Wear!

User Tools

Site Tools


tips:movehands

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
tips:movehands [2016/02/25 21:41] jt3tips:movehands [2016/02/25 21:47] jt3
Line 3: Line 3:
 This tutorial will allow you to smoothly and realistically move the analog hands of a watch face to the 12:00 position (zero) and back to the current time, through the use of a tap action.  In this scenario, "realistically" means not allowing the hands to "blink" into position.  They must move as they would if they were physical objects, bound by the laws of motion. This tutorial will allow you to smoothly and realistically move the analog hands of a watch face to the 12:00 position (zero) and back to the current time, through the use of a tap action.  In this scenario, "realistically" means not allowing the hands to "blink" into position.  They must move as they would if they were physical objects, bound by the laws of motion.
  
-This has been done countless times, and in many ways.  The [[https://plus.google.com/+JamesTaylor3rd/posts/7cgJDCp5Htn|earliest method (that I know of)]] in Watchmaker came long before animation or scripting were available features of the program, and were done purely though tags and maths. Nowadays, it can be done much smoother, much easier, and with very little code.  In fact, recently, I held a "Coding Challenge" to see if the brightest coding minds could come up with an even better solution.  [[https://plus.google.com/u/0/110228601105403324630|Mark Shoulson]] came up with a brilliant one, which is the basis for this wiki.  (For reference, [[https://plus.google.com/u/0/+JamesTaylor3rd/posts/hdgeA9RmsH6|here's the original challenge post]].) +This has been done countless times, and in many ways.  The [[https://plus.google.com/+JamesTaylor3rd/posts/7cgJDCp5Htn|earliest method that I know of]] in Watchmaker came long before animation or scripting were available features of the program, and were done purely though tags and maths. Nowadays, it can be done much smoother, much easier, and with very little code.  In fact, recently, I held a "Coding Challenge" to see if the brightest coding minds could come up with an even better solution.  [[https://plus.google.com/u/0/110228601105403324630|Mark Shoulson]] came up with a brilliant one, which is the basis for this wiki.  (For reference, [[https://plus.google.com/u/0/+JamesTaylor3rd/posts/hdgeA9RmsH6|here's the original challenge post]].) 
  
 So... what's the point?  When would you ever use this?  Well, there are many reasons, but an analog stopwatch is probably the most common.  When activating the stopwatch, you'll want the hands to move to the zero position, and again when you reset the stopwatch.  Then, when you leave stopwatch mode, you'll want to move them back to the current time.  Simulating realistic movement adds to the analog effect, and really adds a sense of realism to your watch face. So... what's the point?  When would you ever use this?  Well, there are many reasons, but an analog stopwatch is probably the most common.  When activating the stopwatch, you'll want the hands to move to the zero position, and again when you reset the stopwatch.  Then, when you leave stopwatch mode, you'll want to move them back to the current time.  Simulating realistic movement adds to the analog effect, and really adds a sense of realism to your watch face.
tips/movehands.txt · Last modified: 2016/02/25 21:55 by jt3