Bug 146361

Summary: View Cursor does not correctly report distance to left margin
Product: LibreOffice Reporter: Robert Simpson <robert>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: UNCONFIRMED ---    
Severity: normal CC: dgp-mail, raal
Priority: medium    
Version: 7.4.0.0 alpha0+   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Basic macro to report position of view cursor.

Description Robert Simpson 2021-12-21 17:12:14 UTC
Created attachment 177063 [details]
Basic macro to report position of view cursor.

The attachment is a simple basic macro to report the current x-position of the view cursor. The result should be the distance, in hundredths of a mm from the left margin. The actual result appears to include any blank space between the left edge of the window and the left edge of the paper.
Comment 1 raal 2022-03-12 16:59:23 UTC
discussion is here: https://ask.libreoffice.org/t/what-is-the-base-for-cursor-x-position-in-basic/71827/8

reproducible from 4.1 to 7.4, change zoom factor is enough to change result of macro. Not sure if it's a bug, leaving unconfirmed.
Comment 2 Dieter 2023-08-30 18:41:57 UTC
Hello Robert, a new major major release of LibreOffice is available since this bug was reported. Could you please try to  reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 3 Robert Simpson 2023-08-31 10:18:19 UTC
Hi Dieter.

No unfortunately the behaviour is unchanged. 

ovc.getPosition().x should report the x-distance of the cursor from the left margin. Currently it still adds the blank space from the left edge of the LO window to the left edge of the paper.

LO 7.6.0.3 (X86_64)
Ubuntu 22.04
Comment 4 Dieter 2023-09-06 16:46:55 UTC
(In reply to raal from comment #1)
> reproducible from 4.1 to 7.4, change zoom factor is enough to change result
> of macro. Not sure if it's a bug, leaving unconfirmed.

Raal, so who should decide about it?