Okay, so today I discovered that my canary file rendered without crashing in the shapeJS co-creator. I've not heard anything from Beekey, but if you did something then thank you!
If it just resolved itself then ... no idea...
So I discovered that the version of my fob generator which I'd left in a cocreator was rendering, but under certain circumstances missing part of the design. Further investigation suggested that it's down to what value the parameters have been given.
For a numeric argument:
positive value -> the value
"0.0" -> 0.0
"0" -> a very long variable string, starting '/tmp', then a long identifier, ending in '.x3db'
"" -> as above.
So it looks like the output filename is getting passed in for zero or unspecified parameters.
Should we call that an unintentional feature?
Incidentally, for shapejs.shapeways.com :
"0" -> 0.0
"" -> undefined
Now obviously, we could work around this in co-creators, but my guess is that it's unlikely to be stable behaviour.
Here's the code I'm running:
Code:
function main(args) {
var text = args[0];
var w=50*MM;
var out=new Text(text,"Roboto",2*w,16*MM,2*MM,0.1*MM);
var grid = createGrid(-w,w,-8*MM,8*MM,-0.5*MM,2.5*MM,0.1*MM);
var maker = new GridMaker();
maker.setSource(out);
maker.makeGrid(grid);
return grid;
}
Just in case anyone else was wondering about drop-down lists and radio buttons - they give the option string, except for the "-- please select...--" string in optional drop-down lists, which gives the filepath.