chrisadolph/tile-simcf — Issue #7: tile Input Checks and Error Messages
Author: chrisadolph
Created: 2012-01-29 20:22:03+00:00
State: open

tile presently does little to check for acceptable inputs, and (mostly as a result) gives nonsensical error messages. tallestGrob error, anyone?

Checks need to happen at least in three ways: checks for each trace, to make sure inputs are feasible for that trace type, checks for tile parameters, to make sure they are possible for a tile plot, and, most difficult, checks for each input to a trace or tile itself conditional on the full range of other inputs to traces and tile.

We never want to accidentally exclude inputs that would work, so if you're unsure if something is an error (just unwise), use ```warning()``` instead of ```error()```.