incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 120498] New: Enhance user experience for editing text in draw shapes and/or tables when using undo/redo
Date Wed, 08 Aug 2012 11:53:23 GMT

          Priority: P3
            Bug ID: 120498
           Summary: Enhance user experience for editing text in draw
                    shapes and/or tables when using undo/redo
          Severity: normal
        Issue Type: DEFECT
    Classification: Application
                OS: All
          Hardware: All
            Status: CONFIRMED
           Version: AOO350-dev
         Component: editing
           Product: drawing

ALG: We have some inconsistencies in Undo/Redo usages when editing text.

(a) For draw shapes:

After starting edit mode (by clicking or by selecting shape and start typing)
Undo/Redo only covers text edit actions, the previous actions are no more shown
in the undo control and/or it's dropdown list. It would be nice to be able to
use undo without having to know that you are in edit mode. Most users do not
understand that they need to exit this mode first to get their undos back. They
end up in pressing undo in edit mode, all edit undos are done and nothing
happens, they are stuck.
There is also the error for new shapes that two additional undo actions (apply
styles/apply attributes) are created which are part of EditEngine/Outliner
setup, but not of text edit; it leads to unwanted effects when undoing these.
This does not happen with shapes which already have text.

(b) For tables:
Same as (a), but even worse when tabbing through the fields; only the currently
edited field can be changed using Undo/Redo (e.g. type in 1st field, tab, type
in 2nd, use undo: no more chance to undo changes in first field). Using Undo
should step back over the fields and on the last change even step back to the
non-edit undos.

Also nice to have: when ending text edit (whatever way) if there is user info
in the current edit redo stack, save it and offer as redo action (not showing
it, but keeping user input as valuable data). Users nowadays do not understand
that data is applied to objects when explicitly ending edit modes (see edit
fields in modern apps, no need to leave the current one).

You are receiving this mail because:
You are the assignee for the bug.

View raw message