bug-gnubg
[Top][All Lists]
Advanced

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

[Bug-gnubg] There _is_ something like multi thread support in GNUbg + sm


From: Holger
Subject: [Bug-gnubg] There _is_ something like multi thread support in GNUbg + small request
Date: Sat, 26 Oct 2002 21:47:55 +0200

Hi all,

I've discovered something that I would regard as a feature, though it's
certainly not intended to be. I'm not sure whether you're aware of it. I
just want to share the fact, maybe you'll find it useful, too (Ian?).

While analyzing a game or match it is possible to browse through it. Just
not anymore with the mouse, but the keyboard shortcuts still work. So with
Page up/down and Ctrl + Page up/down one still can look for instance at the
already analyzed moves. Even the board is updated. It doesn't cause any
problems.

I'm rather happy about this, since this way I don't need to wait 15 min
until the entire match was evaluated until I can look at what I've done
wrong. So, _please_, don't take occasion to disable it.

And since I'm already writing: Could you change the behaviour of Shift +
Page up/down, so that it goes to _after_ the roll, just before the move.
I'd like to see the dice on the board when revising the match. IMHO there
is no benefit to jump in front of the roll, and it's a bit tedious to press
always Page down twice throughout the entire game in order to advance a
full (*) move (and four times if I'm only interested in my moves).
And maybe even better: Swap the shortcuts for Page up/down and Shift + Page
up/down, so that with Shift it steps in half (*) moves, without in whole
(*) moves (IMHO more common so it should have the easier shortcut). There
could even be a feature that advances 2 full (*) moves for browsing the
moves of only one side.

(*) full/whole == roll and move; half == roll | move

Btw, it's inconsistent that Page up needs to be pressed only once to jump
over one move.

Regards,

        Holger




reply via email to

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