Consider a listbox with MultiSelection enabled. Click on one line. It is selected (background put in blue). Press CTRL+A. All lines are displayed as selected (background in blue), but the SelectedValues and SelectedItems properties still contain only the previously selected lines. If one clicks on the first line, then SHIFT+click on the last line, the properties are correct. Teproduced on MS Windows 32 bit and Debian GNU/Linux amd64 (Debian package).
Hello, and thank you for reporting this issue. Can you give a concrete example of which listbox item displays this issue?
(In reply to futureproject from comment #1) > Can you give a concrete example of which listbox item displays this issue? In a database form (not linked to a field).
For complete clarity, I haven't tested it with a listbox linked to a field yet; it may have the same behaviour.
Confirming on Version: 5.2.0.0.alpha0+ Build ID: c93a43c0c9113bc1c787fe6b3c5e58a8bfd80be0 CPU Threads: 2; OS Version: -; UI Render: default; Locale : fr-FR (fr.UTF-8) OSX 10.11.2 Enclosing test file
Created attachment 121882 [details] listbox form with multivalue selection enabled
Actually, I might have misunderstood this in my attempt to reproduce. Lionel, where can you see the properties of your multi-selected values ? I created a Writer document with a single listbox control, containing values entered as a list in the General tab of the control's properties. Whe I save this form and leave form design mode, if I select one or mutliple non-contiguous or contiguous values from the list they all get selected correctly, and simuilarly if I use Ctrl-A to select all of the values. It doesn't seem to make any difference whether I use a dropdown list or just a standard frame showing the complete list of possible values. Resetting back to unconfirmed for the moment, because I get the uncomfortable feeling that I might have misunderstood something somewhere and have not reproduce the buggy behaviour.
Is this a DUP of bug 72932 ?
Created attachment 121885 [details] test case It is easier to see/test with dropdown=false, so I did that. I added a button "show lstBox selected". Select rows with mouse, click on button. Select rows with CTRL-A, click button. You'll see the issue. You need to enable macros.
(In reply to Lionel Elie Mamane from comment #8) > Created attachment 121885 [details] > test case > > It is easier to see/test with dropdown=false, so I did that. > > I added a button "show lstBox selected". Select rows with mouse, click on > button. > Select rows with CTRL-A, click button. You'll see the issue. You need to > enable macros. Ah thanks. My testing on master dbgutil Version: 5.2.0.0.alpha0+ Build ID: 569bbec54030ab4e7f45aa9e832cac3aa36430a3 CPU Threads: 2; OS Version: -; UI Render: default; Locale : fr-FR (fr.UTF-8) OSX 10.11.2 When the form opened, I selected four different values, using the Cmd-left mouse button click combination to do so. The values I selected were One, Three, Five and Six. When I clicked the macro button, I see several messages in sequence (after pressing OK each time) : First message : "There are 4 items selected" Second message : SelectedItems(0) is '0' Third message : SelectedItems(1) is '2' Fourth message : SelectedItems(2) is '4' Fifth message : SelectedItems(3) is '5' Sixth message :There are 4 values selected So, all of this appears to be correct, as the count for the array starts from value index 0. The subsequent messages retrieve the value of the corresponding array index, and return the values I had selected in the GUI. So far so good. Now, I went back to the listbox and selected the first entry, then pressed Cmd-A (select all), and then pressed the macro button : First message : there are 1 items selected Second message : SelectedItems(0) is '0' Third message : SelectedValues(0) is 'One' No other values are shown. Confirming.
** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
It is still present in Version: 6.0.4.2 (x64) Windows 10.
Dear Lionel Elie Mamane, 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
Andreas Heinisch committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1675a68526c43c6c6e4dc850ee911f0c1de75c88 tdf#97066 - When using CTRL-A in a listbox, update selected items It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
@x1sco maybe you could provide the uitest?
*** Bug 103974 has been marked as a duplicate of this bug. ***