After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 727235 - Too much undo steps while nudging
Too much undo steps while nudging
Status: RESOLVED OBSOLETE
Product: dia
Classification: Other
Component: general
0.97.x
Other Linux
: Normal enhancement
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-28 11:38 UTC by treaki
Modified: 2019-03-20 12:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Too-much-undo-steps-for-nudge.patch (4.42 KB, patch)
2014-04-12 20:48 UTC, Hans Breuer 		needs-work Details | Review

Description treaki 2014-03-28 11:38:06 UTC 
if you are moving an object by using the arrow keys on the keyboard there are generated undo steps for every key press. If you than try to use the Undo feature (Ctrl+Z) you just have very few possible steps. You souled: 

1. group the move events together to one undo step
2. give a option to increase the possible undo steps 

greetings
Comment 1 Hans Breuer 2014-04-12 20:46:14 UTC 
In fact there is a way to increase the maximum undo steps (see File/Preferences/User Interface). And there is exactly one undo step for each event, so I corrected the summary.
I've started to hack on it a bit, but am not completely satisfied with the current result. So the patch will be added here rather than with master.
Comment 2 Hans Breuer 2014-04-12 20:48:56 UTC 
Created attachment 274186 [details] [review]
Too-much-undo-steps-for-nudge.patch

The patch includes some idea for improving it. But I may not work on it for a while.
Comment 3 GNOME Infrastructure Team 2019-03-20 12:00:43 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dia/issues/338.