Watchmaker Wiki

The ultimate watch maker for Android Wear!

User Tools

Site Tools

Trace:
tips:tapcolor

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
tips:tapcolor [2015/03/30 19:32] – [Explanation] jt3tips:tapcolor [2015/04/24 05:11] – [Color Field of Object] jt3
Line 1: Line 1:
 ====== Changing Color Through Tap Action ====== ====== Changing Color Through Tap Action ======
  
-A feature that's becoming more and more common, especially with paid watches that can't be edited, is the ability to change the color of an item or items on your watch face via tap action.  This tutorial will explain the most efficient method for doing this.  We'll be using arrays, so you're going to need (at least) version 3.4 of WatchMaker to pull this off.+A feature that's becoming more and more common, especially with paid watches that can't be edited, is the ability to change the color of an item or items on your watch face via tap action.  This tutorial will explain the most efficient method for doing this.  We'll be using arrays, so you're going to need version 3.4 (or higher) of WatchMaker to pull this off.
  
-===== Examples =====+===== Example =====
  
 ==== Main Script ==== ==== Main Script ====
Line 19: Line 19:
  
  
-==== Color Field of Object ====+==== Color Field of Object(s) ====
    var_color1[var_clrnum]    var_color1[var_clrnum]
 ==== Tap Action ==== ==== Tap Action ====
Line 30: Line 30:
 Let's take a closer look at that "var_color1."  This is called an array (or table).  What we've done here is set 7 separate values to the same variable, each being a color in hexadecimal format.  These seven values are comma-separated, and since they're strings, each must have a string identifier.  In this case, we used apostrophes as string identifiers, but you can use quotes if you're one of **those** people :-P.  Just be consistent throughout each array.  Don't mix quote identifiers, or things can get ugly. Let's take a closer look at that "var_color1."  This is called an array (or table).  What we've done here is set 7 separate values to the same variable, each being a color in hexadecimal format.  These seven values are comma-separated, and since they're strings, each must have a string identifier.  In this case, we used apostrophes as string identifiers, but you can use quotes if you're one of **those** people :-P.  Just be consistent throughout each array.  Don't mix quote identifiers, or things can get ugly.
  
-In an array, we determine which value we want like this:  var_color1[1], var_color1[2], and so on.  So, all we need to do to change the color is change the number in the brackets.  That's where var_clrnum comes in.+Since, in an array, a variable can have multiple values, we determine which value we want like this:  var_color1[1], var_color1[2], and so on.  So, all we need to do to change the color is change the number in the brackets.  That's where var_clrnum comes in.
  
 In the script, we set up a function that acts as a toggle.  Each time we call the function, which we'll do via tap action, we increase the value of var_clrnum by one.  When we reach the maximum (the number of entries in our array) value of 7, we simply set it back to 1.  That way, var_clrnum is never a number that does not represent a value in var_color1. In the script, we set up a function that acts as a toggle.  Each time we call the function, which we'll do via tap action, we increase the value of var_clrnum by one.  When we reach the maximum (the number of entries in our array) value of 7, we simply set it back to 1.  That way, var_clrnum is never a number that does not represent a value in var_color1.
tips/tapcolor.txt · Last modified: 2015/04/24 05:16 by jt3