When reintroducing fitCursor, I found again into an old problem that unfortunately we still have.
We want to do a fitCursor after some change to the doc and before the update. Unfortunately the coord cache was not created yet, so we don't have enough information to compute new positions to determine if the cursor is really offscreen... The information again is already there right after the metrics step. So I think that the best solution to avoid a double metrics call is to integrate update and fitCursor. (like a bool fitcursor parameter to update or something). Alfredo
