Bug 345960

Summary:	Forward sync in live preview points to wrong position if "Trim Margins" is set
Product:	[Applications] kile	Reporter:	Oliver Sander <oliver.sander>
Component:	general	Assignee:	Michel Ludwig <michel.ludwig>
Status:	REPORTED ---
Severity:	normal	CC:	frank-fischer, montel
Priority:	NOR
Version First Reported In:	trunk-kde4
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Example LaTeX document

Description Oliver Sander 2015-04-07 19:36:39 UTC

I am using the live preview feature of kile.  This feature shows an embedded instance of okular, which always shows the current state of the compiled document.  Live preview comes with forward syncing: When I move the cursor around in the editor window, there is a corresponding blue horizontal line in the document window which follows the cursor position to the corresponding position in the pdf document.  Unfortunately this stops working when okular's "Trim Margins" feature is enabled (View --> Document Viewer --> Trim Margins).  Then, the blue line still moves, but its position is off.  I suspect that the code that positions the blue line simply doesn't know about the margin trimming, and how that affects how the text is positioned on the screen.

Reproducible: Always

Steps to Reproduce:
1. Open any non-trivial LaTeX document
2. Enable live preview
3. Enable forward sync
4. Move the cursor in the editor window; observe how the blue line follows in the document window
5. Enable "Trim margins"
6. Repeat 4. Observe how the blue line still moves, but its position is wrong

Comment 1 Laurent Montel 2015-04-14 13:17:11 UTC

Could you add "Open any non-trivial LaTeX document" please ?

Comment 2 Oliver Sander 2015-04-14 14:05:06 UTC

Created attachment 92018 [details]
Example LaTeX document

Comment 3 Justin Zobel 2021-03-09 06:59:10 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 4 Frank Fischer 2021-03-09 21:33:26 UTC

At least in version 2.99.2 (on my system) the bug is still there.