Description: UI Linking text boxes with a connector I'm unable to place the end points where I'd like them - ie the connector appears to have other criteria and is placed other than where I want. start point at bottom centre of text box, end point bottom centre of text box 2 .... line connects vetical centre to vertical centre, or top centre to top centre. Relocating points makes no difference as points revert to wherever they want to go. Have tried resizing and moving text boxes - no logic in where connecting line actually connects on each text box. Steps to Reproduce: 1. create and populate x2 text boxes 2. pick a 'connector' and attempt to connect text boxes from bottom centre to bottom centre 3. Actual Results: unable to have connector be from and to the bottom centres of each text box Expected Results: unpredictable placement of connecting line Reproducible: Always User Profile Reset: No Additional Info: surely be connected where the user would like them to be connected?
Created attachment 188377 [details] Screenshot, connection bottom to bottom Screenshot sample.
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 81726f5af5fda25f0d92ffc8458d7f24eb16f408 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Can't produce with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Hello, thank you for reporting the bug. I'm having trouble reproducing the behavior you've described. Is the attached screen shot the desired behavior, and the line snaps to another configuration once you've "let go" of it? Not reproduced in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 46d7119b8be03968017e59d882e5671350304e15 CPU threads: 1; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded or Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Looks like this is in Windows, not Linux, setting Hardware to Windows.
Kevin: Please copy and paste here the contents of your Help - About (LibreOffice - About on macOS) by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Dear kevinturner49, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear kevinturner49, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp