about summary refs log tree commit diff stats
path: root/077trace_browser.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1430Kartik K. Agaram2015-05-221-1/+9
|
* 1429 - third, possibly successful impl of collapseKartik K. Agaram2015-05-221-10/+5
|
* 1428 - second attemptKartik K. Agaram2015-05-221-4/+1
| | | | | This doesn't work either; some children are collapsed but not others (after the first expanded child).
* 1427 - first attempt at collapsing linesKartik K. Agaram2015-05-221-0/+27
| | | | | | Collapsing is harder than expanding. This approach doesn't work because I end up sometimes with visible lines whose parents aren't visible anymore.
* 1426Kartik K. Agaram2015-05-221-4/+0
| | | | | | As often happens, the asserts I come up with fail to survive contact with reality. In this case because the current line may not have anything left to expand.
* 1423 - expand linesKartik K. Agaram2015-05-221-1/+34
|
* 1422 - page-based navigationKartik K. Agaram2015-05-221-3/+34
|
* 1421 - more snappy cursor movementKartik K. Agaram2015-05-221-4/+16
| | | | | Persist the mapping from screen row to trace index between refreshes. Now we have to remember to refresh the mapping anytime we change state.
* 1420 - first steps in cursor movementKartik K. Agaram2015-05-221-0/+8
|
* 1419 - trace browser displays collapsed linesKartik K. Agaram2015-05-221-2/+16
|
* 1418 - starting trace-browser implementation in C++Kartik K. Agaram2015-05-221-0/+66
I still have no idea how it will hook up to the rest. Parsing traces will be slow. I can't test it like this. Writing the large trace data structure to mu memory will be slow. But let's at least see the new algorithm in action. (Not in this commit; so far we just render the first n lines from the chessboard trace, and wait for a 'q' or 'Q' to quit.)