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 643466 - Adding the possibility of "Undo" and "Redo" in tetravex
Adding the possibility of "Undo" and "Redo" in tetravex
Status: RESOLVED OBSOLETE
Product: gnome-tetravex
Classification: Applications
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-tetravex-maint
gnome-tetravex-maint
Depends on:
Blocks:
 
 
Reported: 2011-02-28 10:33 UTC by Bordeau Maxime
Modified: 2018-05-22 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The patch that I propose (10.49 KB, patch)
2011-04-04 09:52 UTC, Bordeau Maxime 		needs-work Details | Review

Description Bordeau Maxime 2011-02-28 10:33:00 UTC 
I've already make a patch which add the options "Undo" and "Redo". They permit to cancel the last tile's movement. I think it's a good idea because this not change the difficulty of the game. Please tell me if you are agree with me and i'll send you the patch.
Comment 1 Bordeau Maxime 2011-04-04 09:52:40 UTC 
Created attachment 185097 [details] [review]
The patch that I propose

This patch add a new feature. It permits to "undo" and "redo" a move.
Comment 2 Robert Ancell 2012-08-31 08:36:08 UTC 
Review of attachment 185097 [details] [review]:

Hi Bordeau,

Thanks for the patch. It will need to be updated for the current version. Undo does seem like a useful feature. Since the toolbar is already a bit cluttered it might be better to only put these items in the application menu and perhaps just undo (i.e. not redo).
Comment 3 GNOME Infrastructure Team 2018-05-22 12:24:14 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/gnome-tetravex/issues/2.