Bug 129467 - Shape Nudge (with Arrow Key) Fails
Summary: Shape Nudge (with Arrow Key) Fails
Status: RESOLVED DUPLICATE of bug 135613
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.0.beta1+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-18 11:40 UTC by DM
Modified: 2023-02-01 20:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample document exhibiting problem (9.47 KB, application/vnd.oasis.opendocument.text)
2019-12-18 11:41 UTC, DM
Details

Note You need to log in before you can comment on or make changes to this bug.
Description DM 2019-12-18 11:40:55 UTC
Description:
The nudging of shapes using the arrow keys is highly erratic. Sometimes it does, often it doesn't.
Attached is a document where if you click the shape and hit the left/right arrow keys does not 'nudge' it.
If you then click in the cell to the right and click back on the shape you still can't nudge it.
If you now drag the shape below outside the table and drag back to where it was you still can't nudge it.
But drag it below outside the table and as an extra click in the aforementioned cell (to the right) and drag it back to where it was and suddenly it is nudgeable!
Click to the right cell again and back again and it becomes unnudgeable once more.

ALSO the nudge steps are far too large - they need to be 1 pixel as viewed on the screen, so you hold an arrow down to move an item then fine tune it with single-presses.

Version: 6.4.0.0.beta1 (x64)
Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920
CPU threads: 2; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: en-GB (en_GB); UI-Language: en-GB
Calc: threaded

Steps to Reproduce:
.

Actual Results:
.

Expected Results:
.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 DM 2019-12-18 11:41:30 UTC
Created attachment 156646 [details]
Sample document exhibiting problem

See Comment 1
Comment 2 Regina Henschel 2019-12-18 17:06:52 UTC
It was almost correct in Version: 5.4.7.2 (x64)
Build ID: c838ef25c16710f8838b1faec480ebba495259d0
CPU threads: 8; OS: Windows 6.19; UI render: default; 
Locale: de-DE (en_US); Calc: CL
Arrow worked
Shift + Arrow worked
Alt + Arrow affects table row height / column width, but faulty.

It is broken in Version: 6.1.0.2 (x64)
Build ID: b3972dcf1284967612d5ee04fea9d15bcf0cc106
CPU threads: 8; OS: Windows 10.0; UI render: default; 
Locale: de-DE (en_US); Calc: CL
Arrow does not work
Shift + Arrow worked
Alt + Arrow affects table row height /column width, now correctly.
There movement for shapes outside table is broken.

Movement of shapes outside a table is currently OK. Movement of cells inside a table cell is still broken. Tested with Version: 6.5.0.0.alpha0+ (x64)
Build ID: 790b5de8941d8f8d98c73ed1343289d7220211ad
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; 
Locale: de-DE (en_US); UI-Language: en-US
Calc: threaded

Outside the table the behavior should be:
Arrow:  move in small steps, "small" depends on grid distance
Shift + Arrow:  move in large steps, "large" depends on grid distance
Alt + Arrow:  move in 1 pixel steps, independent of grid distance

The Alt+Arrow combination is used inside a table to change row height/ column width. But I see no reason, why in case a shape is marked, it does not work on the shape. It should be possible to distinguish the situation "shape is marked" from the situation "cursor is inside cell & nothing marked".

The error here is, that arrows does not move the shape, when the shape is inside a table cell.

An enhancement would be, to make Alt+Arrow work on shapes in cells.
Comment 3 QA Administrators 2021-12-18 03:47:17 UTC Comment hidden (obsolete)
Comment 4 Stéphane Guillou (stragu) 2023-02-01 20:04:49 UTC
Thanks, DM and Regina. I am marking as a duplicate of more recent bug 135613 because this regression was bibisected there already. But I will mention your two comments there.

*** This bug has been marked as a duplicate of bug 135613 ***