Re: [Bug-gnubg] MatchID problem in 0.16 ?

[Jonathan Kinsey]

Jim Segrave wrote:
> On Wed 14 Mar 2007 (13:57 +0100), Massimiliano Maini wrote:
>>> It looks like a bug alright. You can't successfully edit the match id
>>> when the edit button is depressed, it appears to be ignored.
>> Pressed ?
> 
> A button which is pressed can be described as 'depressed'
>   
>>> However, the simplest thing to do is not press the edit button at
>>> all. Simply clear the position id and insert the new one, then clear
>>> the match id and insert its new value. That immediately gives the
>>> desired result.
>> Right, but the behavour is confusing: when the edit button is pressed
>> you cannot alter the matchID, while when it is not pressed you can.
>> Also, the positionID behaves differently (it works with and without
>> the edit button pressed).
>>
>> The integrist position would be to allow editing the matchID and posID
>> only when the edit button is pressed, but that is probably annoying.
>> So let's just allow editing then any time.
> 
> I agree it's a bug, I only was suggesting a workaround. I have no idea
> why changing the match id in Edit mode would be ignored, I have this
> horrible suspicion that there might be a potential problem with it.

The edit "mode" is flawed in that it happens in the gui (front end),
this means that some operations like changing the match id, changing the
current player or clicking undo don't really work as the back-end still
thinks the game is in the pre-edited position (this can mean the
chequers get reset in some cases for example).

I suspect the problem you've found here can be worked around, ideally
the edit functionality needs to be re-written to use the "back end".  A
good test would be if you could edit a position from the command line
interface.

Jon

signature.asc
Description: OpenPGP digital signature