emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#36867: closed (26.2; gamegrid-add-scrore miss lowe


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#36867: closed (26.2; gamegrid-add-scrore miss lower-is-better flag)
Date: Sat, 14 Sep 2019 08:24:01 +0000

Your message dated Sat, 14 Sep 2019 11:23:39 +0300
with message-id <address@hidden>
and subject line Re: bug#36867: 26.2; gamegrid-add-scrore miss lower-is-better 
flag
has caused the debbugs.gnu.org bug report #36867,
regarding 26.2; gamegrid-add-scrore miss lower-is-better flag
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
36867: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36867
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 26.2; gamegrid-add-scrore miss lower-is-better flag Date: Wed, 31 Jul 2019 02:13:18 +0200
The function gamegrid-add-scrore is handy for games developer; they get
a high-score management system with one call. That includes a threshold
for the number of entries in the high-score file.

A consequence of that is, that an entry has be removed from the list if
a new, better one must be inserted. In this situation,
gamegrid-add-scrore currently always removes the "lowest" result.

This is good and well for "more is better" games. But is wrong for
"faster is better" games. An example:
https://github.com/calancha/Minesweeper

This feature omission is on lisp level. The in the emacs sources
included tool update-game-score (which is used by gamegrid, if it is
available) support reverse opperation.



--- End Message ---
--- Begin Message --- Subject: Re: bug#36867: 26.2; gamegrid-add-scrore miss lower-is-better flag Date: Sat, 14 Sep 2019 11:23:39 +0300
> From: Federico Tedin <address@hidden>
> Date: Wed, 04 Sep 2019 00:29:22 +0200
> Cc: address@hidden
> 
> Rolf Ade <address@hidden> writes:
> 
> > The function gamegrid-add-scrore is handy for games developer; they get
> > a high-score management system with one call. That includes a threshold
> > for the number of entries in the high-score file.
> >
> > A consequence of that is, that an entry has be removed from the list if
> > a new, better one must be inserted. In this situation,
> > gamegrid-add-scrore currently always removes the "lowest" result.
> >
> > This is good and well for "more is better" games. But is wrong for
> > "faster is better" games. An example:
> > https://github.com/calancha/Minesweeper
> >
> > This feature omission is on lisp level. The in the emacs sources
> > included tool update-game-score (which is used by gamegrid, if it is
> > available) support reverse opperation.
> 
> I've added a new 'reverse' parameter to gamegrid-add-score that allows
> switching between storing the scores normally, or in reverse order. As
> Rolf mentioned, this feature was already implemented in
> update-game-score. I'm attaching a patch with my changes.

Thanks, pushed to the master branch.

In the future, please mark NEWS entries with "---" if they don't need
to be described in the manuals, and with "+++" if the patch includes
the changes for the manuals.  (I did this for you this time.)


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]