Problem description: Steps to reproduce: as described in https://help.libreoffice.org/Common/Drag-and-Drop_With_the_Data_Source_View , para "Using data in a text document": You can insert a database field in a text document by dragging a field name from the column header of the data source view into the document. This is especially useful when designing form letters. Simply drag the desired fields - home address, form of address, and so on - into your document. Current behavior: a small icon (square) is shown, but no action. Dragging of complete lines is working, resulting in Insert database columns dialog appearing. Expected behavior: Database field is inserted Operating System: Mac OS X Version: 4.1.0.4 release
Correctly working in 4.04 version
Hi, Works fine in 4.1.0.4 on Ubuntu .. Cheers, Cor
OK, dont have currently Ubuntu; Also correctly working with Win7 and Libre Office 4.1.0
FWIW, it works fine in : Version: 4.2.0.0.alpha0+ Build ID: 22d1beb78a475e4846af945afde1c4d6c263b5d6 master build 64bit on OSX 10.8.4 Alex
Hi, So set as WORKSFORME. If you have clear info to reproduce, pls let us know and reopen! Cheers, Cor
I've tried to do some litte Videos to demonstrate the difference of LO 4.0.5 to 4.1.2 under Mac OS X 10.6.8 , hope the second one for 4.1.2 is not too big showing the unexpected behavior. The first shows the convenient behaviour creating a mail merge field by only Drag-and-drop
Created attachment 87905 [details] mail merge demo video for LO 4.0.5
Created attachment 87906 [details] mail merge demo for LO 4.1.2 - file is too big, pls see link https://www.hidrive.strato.com/lnk/4yMXrCoV valid until 20 Nov 13, otherwise leave a message
Why put a video up when it has already been stated this works in current master and future 4.2 ? At some stage, whatever piece of code got fixed will make it into the stable release. Alex
Sorry, Alex, since I'm no software specialist (only Hardware eng.) its not obvious for me to know if there is a difference in 64bit on OSX 10.8.4 or OS X 10.6.8 (running LO as 32bit process). Nevertheless, having a look to the Mac Book Air of my daughter with Lion, it's the same problem. So maybe you're right. Please see my comments as a contribution of a user of LO without code knowledge but also interested in the community and the idea of improving Libre Office. Thanks Ulrich
Comment on attachment 87906 [details] mail merge demo for LO 4.1.2 - file is too big, pls see link set correct mime type ( video/quicktime ) hope that works ;)
Hi Ulrich, Hmm, I understand what you mean. It's sometimes too easy for people working a lot in BugZilla, like me and maybe Alex too.. , to assume that all procedures and notifications are clear as such. thanks for your attachments and the effort you put in making them - though I have trouble using it, sorry If you are able to test a daily build, that would show the current state to you as well. http://dev-builds.libreoffice.org/daily/ regards, Cor
(In reply to comment #8) > https://www.hidrive.strato.com/lnk/4yMXrCoV valid until 20 Nov 13, otherwise > leave a message Could download it via the link and see the problem in that version. thanks again.
Hi, Cor, works correctly as in 4.0.5 and as expected in the daily build libreoffice-4-1~2013-10-22_09.07.34_LibO-Dev_4.0.6.0_MacOS_x86 Hopefully, also in the next /(maijor) version. Thanks and kind regards Ulrich
Do not work in Version 4.5.0.0 Alpha - testet with the actual build (26.03.) on Windows 8.1. It is possible to insert an fieldname via field-insert dialog, but drag and drop do not work. Nothing happend! 2. Problem: If you use the icon "insert data in fields" all fields disappear (or become empty) but no data appears.
(In reply to Thomas Krumbein from comment #15) > Do not work in Version 4.5.0.0 Alpha - testet with the actual build (26.03.) > on Windows 8.1. Hi Thomas, Two notes: 1) Bug does not meet the criteria for Status 'REOPENED' https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/REOPENED#Criteria 2) The last comment on this bug was over a year ago. If you're seeing the same problem in current builds, please open a new bug and link to this bug report using the 'See Also' field. Moving back to Status -> RESOLVED WORKSFORME