--max-file-lag depends on fps about gource HOT 8 CLOSED

If your able to provide a log as an example I'd be curious too what's happening,
though it might be hard to fix.

It does seem kind of an extreme edge case.

I've attached sample log. Run it with "gource --max-file-lag 0.001 log.txt"
Log has one commit with 1500 files added and as I understand --max-file-lag 
option, it 
should take ~1.5sec, but it takes much longer...

I think the number of log records read is frame rate based, and the custom log 
format
has only one file per record, so it's going to take 25 seconds at 60fps to add 
1500
files.

I guess a work around would be some sort of --max-records-per-frame option.

In my opinion it's better to completely remove frame rate dependency instead of 
making 
strange options that depend on user hardware and OS.

I've changed it so now a contiguous block of records in the custom log with the 
same
username and timestamp are considered the same commit, so max-file-lag will 
work:

http://gource.googlecode.com/files/gource-0.24-beta2.tar.gz

Thanks a lot! I'll wait for official release since I'm using windows-build of 
Gource.

And here it is:
http://gource.googlecode.com/files/gource-0.24.win32.zip

Works great, thank you!