Closed pyk1998 closed 6 months ago
This is a limit by SyncTeX. You can try synctex.synctexjs.enabled: false
without guarantee.
Confirmed that this is a synctex issue. The offset values passed from synctex (either binary or .js) is incorrect. I'm afraid we can't do simple calibrations from the extension side.
Confirmed that this is a synctex issue. The offset values passed from synctex (either binary or .js) is incorrect. I'm afraid we can't do simple calibrations from the extension side.
@James-Yu Thank you for the inspection. I've also checked the results from synctex binary, and it contains a list of records. Follow the code handling the records, it uses the last one directly.
However, the synctex commandline says (synctex view help
):
The result is a list of records. In general the first one is the most accurate but
it is the responsibility of the client to decide which one best fits the user needs.
I have tried to change to use the first return record, but it is also inaccurate.
Are there any ideas (or references) of how to do calibration? I'm planning to reference the implementation of other opensource externel PDF viewers (e.g. Sumatra PDF) handling the synctex results?
I don't think a precise calibration would be possible without significantly tinkering synctex itself. That is way beyond the scope of this extension, though.
Pre-checks*
Environment*
The Issue*
Reproduction Steps
Expected Behavior
Logs
LaTeX Workshop Output*
INFO [perf] Render performance baseline is 15ms