Description: Calling removeByIndex removes the row for the corresponding index and does not remove the corresponding column. Steps to Reproduce: 1. Get XColumnRowRange. 2. Get XTableColumns from the obtained XColumnRowRange instance. 3. Call removeByIndex() from the obtained XTableColumns. Actual Results: Supposed to remove the column for the corresponding index Expected Results: Removes the row instead Reproducible: Always User Profile Reset: No Additional Info: Tested out with C# .NET Frame 4.7.2 on windows 10 (build 14393) with Visual Studio 2019.
Can you please prepare a document with a script to reproduce?
(In reply to Samuel Mehrbrodt (CIB) from comment #1) > Can you please prepare a document with a script to reproduce? Should I attach .cs file?
Created attachment 155836 [details] Exampe C# file with the bug in question
[Automated Action] NeedInfo-To-Unconfirmed
Created attachment 155883 [details] removeColByIndex.bsh
Created attachment 155884 [details] removeColByIndex.ots
added a beanshell and macro example, also tried with java using remote connection (LO 6.3.3.2) - scripts will always remove columns.
(In reply to Oliver Brinzing from comment #7) > added a beanshell and macro example, also tried with java using remote > connection (LO 6.3.3.2) - scripts will always remove columns. Vignesh: please comment on Oliver's test case.
Dear vigneshnama95, 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 vigneshnama95, 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