Created attachment 91291 [details] a spreadsheet with data that behaves like explained. The macro is to be recorded manually. Problem description: I recorded a macro which deleted G column. While applying it again it deletes always the A column instead the column that should have been recorded. Steps to reproduce: 1. create some columns filled with anything, starting from A, or use the attached file (about one stock values, easy to read). 2. Record a macro which deletes (not the values, the whole column) G column 3. open back the initial file 4. apply the recorded macro Current behavior: it deletes always the column A Expected behavior: it should delete the G column that was recorded in the macro. Operating System: Mac OS X Version: 4.1.4.2 release
I gave a try with master sources updated today. In tests I did, it deleted the column where the cursor was.
Julien beat me to it, but here is the comment I had prepared. Starting from scratch, I recorded a macro while I selected column C (by mouse click on the column heading) and deleted the column from the pop-up menu. The recorded macro did not capture the selection operation. Thus, in playback, the macro deletes each column that has a selected cell. For comparison: (*) a macro recorded in Writer does copture selection done by <shift>+<right-arrow>. (*) a macro recorded in Calc does capture selection by mouse-click on a cell and following <shift>+<right-arrow> <shift>+<down-arrow>. My observations are in a debug build of master commit 480c7c2, fetched 2013-12-27 02:33 UTC. So I am setting platform = All.
This time fer shur, Rocky.
still reproducible with LibO 4.3.2.2 under Win7x64 (In reply to Terrence Enger from comment #2) > ... The recorded macro did not capture the selection > operation. Thus, in playback, the macro deletes each column that has > a selected cell. > > .... yes, this is exactly what happens. this is the recorded code which is the same as in OOo 3.3.0 sub test rem ---------------------------------------------------------------------- rem define variables dim document as object dim dispatcher as object rem ---------------------------------------------------------------------- rem get access to the document document = ThisComponent.CurrentController.Frame dispatcher = createUnoService("com.sun.star.frame.DispatchHelper") rem ---------------------------------------------------------------------- dispatcher.executeDispatch(document, ".uno:DeleteColumns", "", 0, Array()) end sub so we are dealing with one of the limitation of the macro recorder which is inherited from OOo.
** 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.0.4 or later) 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Running daily dbgutil bibisec repo version 2015-12-20 in an environment chroot'd to debian sid, I see that "record macro" does not capture the selection of a column made by clicking on the column heading. So the problem still happens.
The current macro recorder only records commands executed via the dispatcher. It's not designed to record user actions, and there is no way to "fix" it, other than rewriting from scratch. There is a very good reason why the checkbox in Tools->Options has the word "limited" in it.
Thank you, Maxim. I am setting bug status RESOLVED WONTFIX.