Hi 1 - I write "azerty" in A1 (in LibreOfficeCalc) 2 - I cut A1 and I paste in A3 3 - If I do "CTRL Z" : A1 and A3 are empty ! 4 - I have to do "CTRL" Z a second time for retriving "azerty" in A1 I think that "cleaning a move" is "cleaning a move" and not "half a move". Greatings == JLC
(In reply to comment #0) > Hi > > 1 - I write "azerty" in A1 (in LibreOfficeCalc) > 2 - I cut A1 and I paste in A3 > 3 - If I do "CTRL Z" : A1 and A3 are empty ! > 4 - I have to do "CTRL" Z a second time for retriving "azerty" in A1 Behavior confirmed on Ubutu 12.04.4 LO Version: 4.4.0.0.alpha0+ Build ID: fc49c052dbdbb5ab3b0a02a13143705f769b9662 > I think that "cleaning a move" is "cleaning a move" and not "half a move". > Good question. I tried the same test with Gnumeric Spreadsheet 1.10.17 and current Google Docs 'Sheets' application, and got the results you expected (after the Undo operation, A3 was empty and A1 was restored to 'azerty'). So the LibreOffice behavior appears to be unique. Do you happen to have access to MS-Office? What's the behavior there? Interestingly, a very similar bug 50843 (relating to COPY-paste, then Undo) was reported/fixed a while ago. Too bad they didn't try CUT-and-paste!
Improve summary
(In reply to comment #1) > Do you happen to have access to MS-Office? What's the behavior there? MS-Office has it as a single undo. When seeing it, i see it doesnt actually cut the contents from the cell until you paste it, so it acts similar to copy.
Reproduced on Ubuntu 12.04 x86 with: - LO 4.2.5.2, 4.0.6.2, 3.5.7.2 - AOO 4.1.0 So LO, like AOO, thinks that 2 operations (cut & paste) must be restored to original position with double (2) undo. But Kingsoft 9 only needs single undo, just like MSO as Jay observed
Created attachment 101472 [details] attachment-6751-0.html Hi 1 - With Excel 2002 (10.6871.6870) SP3 "cut-paste" is restored with only one "undo" 2 - As you can see on the sceenshoot *Capture du 2014-06-21 10:49:14.png* the first "CTRL Z" is "Annuler:déplacer" (i.e. "Undo:move"). It should be "Undo:paste". If "Undo:move" appear in the menu, you have to undo move At this time, "Undo:paste" should be write in place of "Undo:move" Greatings == JLC Le 21/06/2014 09:10, bugzilla-daemon@freedesktop.org a écrit : > ign_christian <mailto:ign_christian@yahoo.com> changed bug 80188 > <https://bugs.freedesktop.org/show_bug.cgi?id=80188> > What Removed Added > See Also https://bugs.freedesktop.org/show_bug.cgi?id=65217, > https://bugs.freedesktop.org/show_bug.cgi?id=74264 > Version 4.2.3.3 release 3.5.7.2 release > > *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=80188#c4> > on bug 80188 <https://bugs.freedesktop.org/show_bug.cgi?id=80188> from > ign_christian <mailto:ign_christian@yahoo.com> * > Reproduced on Ubuntu 12.04 x86 with: > - LO 4.2.5.2, 4.0.6.2, 3.5.7.2 > - AOO 4.1.0 > > So LO, like AOO, thinks that 2 operations (cut & paste) must be restored to > original position with double (2) undo. > > But Kingsoft 9 only needs single undo, just like MSO as Jay observed > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. >
Created attachment 101473 [details] attachment-6751-1.dat
Created attachment 101474 [details] Capture du 2014-06-21 10:49:14.png
** 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 (4.4.1 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Still repro. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 186f32f63434e16ff5776251657f902d5808ed3d TinderBox: Win-x86@39, Branch:master, Time: 2015-10-16_09:42:47 Locale: en-US (fi_FI)
** 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.1.6 or 5.2.3 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-20161108
Dear jlc, 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
repro Version: 7.0.0.0.beta1 (x64) Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-US Calc: threaded
It seem to me not a bug. If you cut and then paste, there are two different actions. Then you will need to undo twice. If you drag, that is a single action.
Dear jlc, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Same in OOo 3.3, so behaviour is inherited. Same in recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ec60d354359067f8c5c686ef2239ee705916de43 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded However I agree with Leroy that a cut and paste action is a two-step process, and that two undos are needed. Imagine you paste at the wrong spot. I think being able to just undo the paste action is a plus when compared to other suites. Office.com currently has the UI of greyed-out contents in cut cell until it is pasted, which does visually hint at it being considered a single action. Design team, thoughts?
What if cut is (ab)used to delete content? It's clearly a two-step thing and NAB.