Description: It is not possible any more to select Cell range for Y error bars. Manual entering of Cell range is still possible. Steps to Reproduce: 1.Open attached file and enter chart by double mouse click on it. 2.Select data series by mouse click on it. 3.Select Insert > Y error bars. 4.Select Cell Range in Error Categories. 5.Mark Same value on both (not mandatory). 6.Push button on the right to Select data range. 7.Try to select cell range C1:C8. Actual Results: It is not possible to select cell range, however it is possible to enter it manually (Sheet name should be included, respectively T1.C1:C8). The window for selection of cell range can be closed only by clicking Enter on keyboard. Expected Results: It should be possible to select cell range by mouse. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 149566 [details] Chart for reproduction of the problem
Created attachment 149583 [details] chart error bar
i can confirm this problem with: Version: 6.2.1.1 (x64) Build ID: 757c58e8cb70b2982843211a54750fb3cd79acd5 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: and lo crashes if one closes the "Y Eror Bars for Data Series "Column B" dialog, while "Select Range for Positive Error Bars;Area" dialog is open
no crash with: Version: 6.1.5.2 (x64) Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc:
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=8947c9b1d8cd407131fdfb6fc3c77c8532e9d2a0 author Caolán McNamara <caolanm@redhat.com> 2018-10-18 13:00:41 +0100 committer Caolán McNamara <caolanm@redhat.com> 2018-10-20 13:52:34 +0200 commit 8947c9b1d8cd407131fdfb6fc3c77c8532e9d2a0 (patch) tree f47becc099d139ae601fc41d9e8f49f24672f0e0 parent b361413eef7e46f340d921708faca9986c63c9f8 (diff) weld SchAttribTabDlg Bisected with: bibisect/bibisect-linux64-6.2 Adding Cc: to Caolán McNamara
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/d02381a70184f13031e5f2e19a837f5821e4a49c%5E%21 Resolves: tdf#123694 we need the controller, not the tabpage parent It will be available in 6.3.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.
fixed in master, backports in gerrit
Verified in Version: 6.3.0.0.alpha0+ Build ID: c196d70337f6b755cfc4c34beda05554c6fab114 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded @Caolán, thanks for fixing this issue!
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/6ca6ca12f96524c9f68dad94b2857d98ca12134a%5E%21 Resolves: tdf#123694 we need the controller, not the tabpage parent It will be available in 6.2.3. 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.
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-6-2-2": https://git.libreoffice.org/core/+/8e8029a891540664ac0ce59b23d586aefb5fe77c%5E%21 Resolves: tdf#123694 we need the controller, not the tabpage parent It will be available in 6.2.2. 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.
*** Bug 124090 has been marked as a duplicate of this bug. ***
Closing as VERIFIED FIXED
The problem is solved in 6.2.3.1. Thanks!