Bug 34827 - EDITING: no undo for visible area modifications
Summary: EDITING: no undo for visible area modifications
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Libreoffice (show other bugs)
Version: 3.3.1 release
Hardware: All All
: medium minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 04:42 UTC by sasha.libreoffice
Modified: 2014-03-10 20:20 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
explanation and screenshots of undo problem (61.48 KB, application/vnd.oasis.opendocument.text)
2011-02-28 04:42 UTC, sasha.libreoffice
Details

Description sasha.libreoffice 2011-02-28 04:42:30 UTC
Created attachment 43922 [details]
explanation and screenshots of undo problem

To demonstrate this problem I have inserted picture in Writer as OLE-object. We can not undo object after editing. Maybe objects should be undoable. But only LibreOffoce-objects.
Used LibreOffice 3.3.1.2 Mandriva 64 bit Kde 4.4 and windows xp 32 bit
In attachment explanation and screenshots of undo problem.
Comment 1 Rainer Bielefeld Retired 2011-05-22 10:54:46 UTC
[Reproducible] with "LibreOffice 3.4.0RC1  – WIN7  Home Premium  (64bit) German UI [OOO340m1 (Build:11)]".
It's some  inconsequent / inconsistent OLE object view handling causing this problem.

After the object view has been modified in reporter's sample the "Save" icon appears, that shows that LibO has recognized that the document has been modified. But there is no undo possibility, and that is wrong.

This IMHO is an aspect of a more general problem I reported as a.m. OOo bug. 

For me that's not trivial. If yo edit a linked (in many documents) DRAW object, you will become desperate trying to get in to the correct position in all documents. I have learned to live with that prolbem (co not edit objects, create new ones for use in later documents), but it's dissatisfying.
Comment 2 Björn Michaelsen 2011-12-23 11:47:17 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 sasha.libreoffice 2012-01-02 01:51:28 UTC
reproduced on LibO 3.5.0 beta 1
Comment 4 Rainer Bielefeld Retired 2012-01-02 02:03:56 UTC
@sasha:
Migt be a feature and not a bug?
When I enter a Textbox-"X", leave OLE object, Type "1234", I can undo that "1234" with the undo icon immediately or,when I enter the OLE object, the undo icon wil undo the "x". That looks like independent undo stacks, and that IMHO is rather useful.

What do you think?
Comment 5 sasha.libreoffice 2012-01-02 02:20:57 UTC
If user intendedly changes OLE object, then this is indeed feature. But in this bugreport is another situation:
User unintendedly (accidentally) scrolled OLE object (not changed). Initial document becomes look different. And user press Ctrl+Z to restore it initial look. But nothing happens.
I expected that using Undo I can restore document to it initial look (state). My be all changes inside of OLE can appear as one step of undo outside of OLE.
Comment 6 Rainer Bielefeld Retired 2012-01-02 02:40:19 UTC
Indeed, now I understand my Comment 1 again.
Comment 7 A (Andy) 2014-03-08 21:33:58 UTC
for me not reproducible with LO 4.2.1.1 (Win 8.1)

This bug seems to be resolved in the latest release of LO.
Can anybody still confirm this bug?  Otherwise, I would propose to close this issue as Resolved.
Comment 8 sasha.libreoffice 2014-03-10 20:20:10 UTC
reproduced in 4.2.0 on Fedora (RFR) 64 bit


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.