The drawing half of the evaluation graph; eval_graph_geometry() does the
arithmetic. This lives in the app layer rather than beside the tracker
because it is the one place a UI toolkit is needed, and the core is kept
free of one - see test-core-boundary.R.
Arguments
- cp
Centipawn evaluations from White's point of view, one per position (so one more than the number of moves).
NAwhere not yet measured.- click_input
Namespaced Shiny input id to report clicks to, or
NULLfor a static graph. Each point reports its own index asply, counting the moves played to reach it - so 0 is the opening position, and every other value names the move that arrived there.- width, height
Pixel size of the graph.