RE: [Bug-gnubg] Handling ambiguous checker moves

[Ian Shaw]

> 
> > For the "click on starting point" way of moving, this is rather 
> > natural, but for the "drag to destination", it's less 
> clear. In case 
> > of an ambiguity, I prefer a criterion like "if the checker wasn't 
> > dragged on this point, it didn't land there".
> 
> An interesting thing can be said about this. The way to 
> remove the entire problem and simplify things could also be 
> done by not allowing a drag to a destination that can't be 
> done in one roll - Period.
> 

I hate that idea. If I drag 21: 13/10, it would be really annoying to
have to choose between 13/11 11/10 and 13/12 12/10.

Having read through all the arguments, I think that always playing the
higher die first is the best suggestion. Then we are not asking gnubg to
make a choice of the user's intent; we are implementing a fixed
interpretation of a user's command from the gui. 

But I can't say it will detract from my gnubg experience if no change is
made at all.

Just my 2 cents.
-- Ian