Bug 59254 - EDITING: order of columns of data grid table not changeable by mouse movement
Summary: EDITING: order of columns of data grid table not changeable by mouse movement
Status: RESOLVED DUPLICATE of bug 54021
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: regression
Depends on:
Reported: 2013-01-11 17:46 UTC by Biofjöd
Modified: 2013-01-12 21:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Biofjöd 2013-01-11 17:46:09 UTC

When in design mode, the order of columns of a data grid table cannot be changed anymore by pressing and holding the left mouse button on the column's header and moving it to left or right.

Current behaviour:

A mouse pointer is shown making an "add item" appearance, and no movement of the column occurs. When the left mouse button is released, the mouse pointer changes back to ARROW with no column movement having happened.

Expected behaviour:

As in earlier versions of LO, the user can change the columns' order by dragging.
Comment 1 Alex Thurgood 2013-01-11 18:18:31 UTC
Confirming also on master daily build from Jan 6th, 2013, Mac OSX 10.8.2.

It was not made clear that the initial reporter was referring to a Form containing a table grid control.

In LO 3.3.4, for example, I can create a form having such a grid control in Form Design mode, and move the field column order around. Even if I just open the form normally for browsing/data entry once it has been saved, I can also move the columns around.

However, in the master daily build mentioned above, this is no longer possible, either in Form Design mode or data entry/browse mode.

Clearly a regression. As it affects other OSes too, changing to All.

Putting Lionel on CC and upping priority.

Comment 2 Robert Großkopf 2013-01-12 21:04:06 UTC

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