Correct image capture time

[agasser]

Timer.getFPGATimesptamp() returns the current time in seconds, but res.getLatencyMillis() is in miliseconds.

Fixes #498

[shueja]

How does this commit fix the issue? Don't you need to multiply one or divide the other by 1000?

[agasser]

Yikes, I don't know how I managed to get that wrong. It's fixed now.

[gerth2]

yup

[gerth2]

Nitpick - d is possibly going to cause some lack of resolution if millis ever returns a fraction. And also might be confusing to a newbie not familiar with the syntax (since that line shows up with the docs). But I don't think it's worth blocking a merge till we know there's a real issue.

[agasser]

Nitpick - d is possibly going to cause some lack of resolution if millis ever returns a fraction.

Can you explain?

I'm fine just using an integer or using 1000.0 if its easier to read.

[gerth2]

1000.0 would be my preference - simply because it still reads well, and future-proofs against keeping things floating point. Which, as far as I know, is generally "best practice" for FRC hardware and purposes.