### The Ikea Lillabo Processing code

By popular demand... here's the code, written in Processing that actually draws the train sets. I hadn't released it because I didn't think it was very interesting, but you are welcome to it.
`// --------------------------------------------------------------------------//// Small program to draw pictures of Ikea Lillabo track layouts using// instructions derived from my Perl program.//// Written by John Graham-Cumming (http://www.jgc.org/)//// Released under the General Public License, version 2//// --------------------------------------------------------------------------// This is the cursor position (x, y) coordinates and angle to the // horizontalfloat x, y, a;// The length in pixels of a single straight piecefloat len = 40;// See the Perl program for a full explanation, but there are 8 curves// in a circle and from that the radians of curve arc, the length of the// straight line between the curve ends and the curve angle to the // horizontal can be calculated.float curves_in_circle = 8;float radians_in_curve = 2 * PI / curves_in_circle;float curve_angle = radians_in_curve / 2;float curve_length = len * 2 * cos(PI/2 - radians_in_curve/2);// The Processing equivalent of main()void setup() {    // Set up the basic parameters for the drawing: a 1000x1000 canvas,  // with a white background.  None of the elements drawn will be filled  // and the lines will be four pixels wide.    size(1000,1000);  background(255,255,255);  strokeWeight(4);  noFill();    // These are the nine possible layouts discovered by the Perl program  // and were copy/pasted here.  Clearly this would be better done  // dynamically with this program reading the Perl program's output.    int layouts = 9;  String s[] = new String[layouts];      s[0] = "AAAACCAAAASSAAB";  s[1] = "CCCCCCSSAAAAAAB";  s[2] = "CAAAAACASSAAAAB";  s[3] = "CAAAAASCASAAAAB";  s[4] = "CAAAAASSCAAAAAB";  s[5] = "AAACAACAAASSAAB";  s[6] = "ACAAAASACSAAAAB";  s[7] = "ACAAAASSACAAAAB";  s[8] = "AACAAASSAACAAAB";  // (row, col) is the row and column position of the next layout to draw  // starting from the top left of the canvas.  Since we know there are  // 9 the loop below lays them out 3x3.  h is the height of space  // reserved for a layout.  int row = 0;  int col = 0;  int h = 250;  int w = h + 50;  for ( int j = 0; j < layouts; j++ ) {          // Start 200 pixels from the top left corner and with an initial      // angle of 0            a = 0;      x = 200 + w * col;      y = 200 + h * row;      col++;             if ( col == 3 ) {          col = 0;          row++;      }      for ( int i = 0; i < s[j].length(); i++ ) {       switch(s[j].charAt(i)) {          case 'B':            bridge();            break;          case 'C':            clockwise();            break;          case 'A':            anticlockwise();            break;          case 'S':            straight();            break;       }    }  }}// Function to draw a piece and update (x, y) and avoid draw_piece( float l,    // Length of piece to be drawn                 float ang ) // The angular change due to the piece{  // If the ang is zero then this is a straight piece so use line(), if  // non-zero then it's a curve and so use arc()    if ( ang == 0 ) {    // (dx, dy) is the end of the piece truncated (the 0.8 multiplier)    // to leave a little gap between pieces.        float dx = x + l * 0.8 * cos(a + ang);    float dy = y + l * 0.8 * sin(a + ang);    line( x, y, dx, dy );  } else {    int h = (ang<0)?-1:1;        // (ox, oy) is the location of the centre of the circle on which the    // arc we are drawing lies.  s and e are the starting and ending angles    // of arc to draw. Note that s must be less than e.  Note the 1.5 here    // is used to shorten the arc to leave a small gap between pieces.        float ox = x - h * len * cos(PI/2-a);          float oy = y + h * len * sin(PI/2-a);      float s = a;    float e = a + ang * 1.5;    if ( s > e ) {      float t = e;      e = s;      s = t;        }        // The PI/2 adjustment here is needed because the angles in s and e are    // derived from a which is to the horizontal and the arc() function needs    // angles to the vertical        ellipseMode(CENTER);    arc( ox, oy, len*2, len*2, s - h * PI/2, e - h * PI/2 );  }  // Update (x,y) and a to be at the end of the new piece that's been  // added and with the correct orientation.    x += l * cos(a + ang);  y += l * sin(a + ang);  a += 2 * ang;}// Four functions to draw the four pieces giving them different colours.void bridge(){  stroke(255,0,0);  draw_piece(2*len,0);}void straight(){  stroke(0,255,0);  draw_piece(len,0);}void clockwise(){  stroke(255,0,255);  draw_piece(curve_length,curve_angle);}void anticlockwise(){  stroke(0,0,255);  draw_piece(curve_length,-curve_angle);}`

Unknown said…
Thanks for posting the graphics code. I've been playing with both the generator and display code some today.

I was interested in the designs for two sets. I have it running with the second bridge as two straight sections. It's got about 1250 layouts generated so far. Some of them are not buildable due to stacked tracks. I'm thinking on how to check for this condition.

### Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

### All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands . They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0 image by Shinji I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring): The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30). The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {     float m = (360-30*float(h))*2/13;     int s = round(60*(m-floor(m)));     int col = h%6;     int row = floor(h/6);     draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1),

### The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of