The only possibility here: the tree is not set up correctly . . .
commite279a70bf3a9c2b6638e4d3618c9960265db91ce
authorstrange <kawk256@gmail.com>
Mon, 22 Feb 2010 19:37:20 +0000 (22 12:37 -0700)
committerstrange <kawk256@gmail.com>
Mon, 22 Feb 2010 19:37:20 +0000 (22 12:37 -0700)
tree5a3fe3374b43d5daa7248e0e9f5be1f1a1e0bfe3
parent783b9e94ee913b2455a08f584efc0653d456d554
The only possibility here: the tree is not set up correctly . . .

If I show exactly what is happening in count_blocks(), it shows that it is
only acting upon the state of the tree in snapshot #1. Also, the nice qDebug()
statement is showing that the new blocks are always being added to the first
snapshot's head element.

In other words, I need to pin down exactly where the tree is going wrong . . .
gui/src/session/Visualization.cpp
gui/src/session/visualizations/ActiveBlocksRequest.cpp
gui/src/storage/FreeEvent.cpp