Feature Request: seek not clear stage, but calculates situation based on --file-idle-time

[GoogleCodeExporter]

I'm interested in when codebase has structural modifications, e.g. some 
directory is entirely removed.

Steps:
I'm running gource with no hiding idle nodes automatically at all (-i 1000000). 
I start visualization with -p 0.5 (or seek with timeline).

Actual output:
The stage starts empty (or seeking: stage will be cleared).

Wished output:
Stage is on exactly same situation than I was really watched it to this frame.

What version of the product are you using?
git: da74ace818261ea6653f71ace15d1cd2ebb4bd47
Date:   Mon Sep 6 17:30:10 2010 +1200

Original issue reported on code.google.com by aapo.rantalainen on 9 Sep 2010 at 10:07

[GoogleCodeExporter]

A quick suggestion, though not a solution to your issue; to turn file-idle-time 
off, use -i 0 instead of -i 1000000.

Also, to make your issue clearer to understand, consider posting screens of 
what output you expect to see and what output you're actually getting.

Original comment by skoobiedu@gmail.com on 17 Apr 2011 at 5:30

[GoogleCodeExporter]

Thanks for -i 0. But that was not what I'm asking.

I made mockup images for actual and expected outputs.
Start "./gource -i 0 -p 0.14"
Take screenshot immediately.

Original comment by aapo.rantalainen on 18 Apr 2011 at 5:34

Attachments:

• actual.png
• expected.png

[GoogleCodeExporter]

Hi. It's a cool idea, it's worth investigating. The bottleneck is reading and 
parsing the entire log between the current and seek position to and applying 
those changes to the tree.

Cheers

Andrew

Original comment by acaudw...@gmail.com on 18 Apr 2011 at 7:35

• Added labels: Type-Enhancement
• Removed labels: Type-Defect