Created attachment 138824 [details] database to demo form table control field copy Bug 54021 addresses moving a base form's table-control field. Until that's fixed, and it's been 5 years, there's a workaround which allows copying a base form's table-control field. The idea is that copy + delete = move. With the workaround the mouse drag does copy, not move. Copy works, but barely. This bug: The copy done is a shallow copy and doesn't copy the field as it is, but rather copies it as it was originally created, or as it might be created if newly created. For example it doesn't copy any new name, label, SQL, or object type. Steps to reproduce: * Open the attached database with LO 6. * Edit the form named 'Table1'. (Tip: the procedure in 54021 comment 34 is very similar to this one and probably should be reviewed before this procedure.) * Do the workaround described in 54021 comment 33, (right click on a field header, then cancel the shortcut menu). * Use the left mouse button to drag a field right (or left). The mouse pointer shows a "+" (for copy). Expected result: the new field created should be identical to the field copied. Actual result: When you release the mouse button a new field is inserted which is a partial copy of the field you dragged. But this new copy is not identical to the field that was dragged to copy it. It is more like a freshly created field, like if it were appended. For example if it had been previously changed into a combo box those changes are disregarded. Also properties like the width, name, label, etc are disregarded. Tested on LO 6 on linux Debian 9.3.
Copying of a field never worked right. See bug 54021 https://bugs.documentfoundation.org/show_bug.cgi?id=54021#c0 I have tested it a little bit more. Copying is impossible with older versions, but has become possible in LO 5.* with the workaround you described, also by clicking on the tableheader with left mousebutton twice. But it's no copy. There is only created a new field for text with the same header as the existing field. You could copy comboboxes, listboxes - all copies will be textfields. I will set the version to the first LO-5.0 Could be there is a workaround for older versions, too. But copying without right content and workaround and only show a symbol for copying - seems to be very buggy. Testsystem here: OpenSUSE 42.2 64bit rpm Linux.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Have tested again with LO 6.2.0.1. You could "copy" a field, which has connection to a database field. This fields differs from the source field: 1) It is every time a text field, connected, for example, to an Integer of the database. 2) The label of the field changes to the name of the field of the database table, doesn't copy the label of the tablecontrol of the form. So only part which is copied is the connection to the datasource. It is the same buggy behaviour as described in the bug-description. Tested with Version: 6.2.0.1 Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 CPU threads: 6; OS: Linux 4.12; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded
Have tested again while making screenshots for LO-Base-Handbook. If I click with right mousebutton on the field and then with the left and move the mouse the field will be copied. The copy will have the same content as a field, which is directly created through the wizard. Listboxes in a tablecontrol aren't copied as listboxes. The connection to the data-field will be copied, also the field, which would be created by the wizard (numeric field, for example, for a foreignkey). If I create a new tablecontrol the copying of the field will work without the mousebutton-problem, but the result will be the same. A created listbox won't be copied as listbox. All changes you have made after creating the tablecontrol will be lost in the copy.
Dear Howard Johnson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Howard Johnson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still the same. "Copying" a listbox or a combobox won't copy the field content but copies a numeric field (listbox) or a text field (combobox) with connection to the datasource. Tested with LO 7.4.5.1 ob OpenSUSE 15.3 64bit rpm Linux