"The user has the ability to make the play they want"
Yes, but the user has to know how his action will be interpreted, and that interpretation should make sense intuitively. If I slide a checker directly from 6 to 3, I don't expect that to be interpreted as 6/5*/3. Of course I can undo the move and replay it in a "clearer" way. But I think Philippe's reply makes sense; there is simply a small problem in how gnubg is currently interpreting certain actions. Fix that, and no extra prefs or complications are needed.
In the case, maintaining the status quo seems wrong.
----- Original Message -----
From: "Michael Petch" <address@hidden>
To: "Jonathan Kinsey" <address@hidden>, address@hidden, "Philippe Michel" <address@hidden>
Sent: Thursday, April 9, 2009 2:59:12 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Bug-gnubg] Handling ambiguous checker moves
On 09/04/09 2:22 AM, "Jonathan Kinsey" <address@hidden> wrote:
I just explicitly enter ambiguous moves, either by dragging twice or using theI wholeheartedly agree with Jon.
left/right mouse buttons. I can't see any problem with gnubg interpreting an
ambiguous drag as a pick-n-pass as that's generally the most likely move in
My opinion is that GnuBG’s interface needs to become more streamlined. Adding more options or features to handle cases like this makes little sense. People can use Drag/Drop or the buttons to control which piece to move first. The user has the ability to make the play they want, so I say maintain the status quo.