Bug 401243

Summary:	Move numbers "skip" when a stone is captured.
Product:	[Applications] kigo	Reporter:	Glen K. Peterson <glen.k.peterson>
Component:	general	Assignee:	Sascha Peilicke <saschpe>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kde-games-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Correct move numbers before capture Incorrect move numbers after capture

Description Glen K. Peterson 2018-11-20 18:41:00 UTC

SUMMARY
When a stone is captured, that stone's move number is lost.

STEPS TO REPRODUCE
1. Black plays move 20
2. White plays move 21 to capture the black stone.
3. When you click on "show move numbers" at the end of the game, white's play is now numbered "20" and subsequent move numbers continue from there.

OBSERVED RESULT
The original move 20 is lost and move 21 is now numbered "20".

EXPECTED RESULT
The moves are remembered and numbered in order, period.  Capturing should not change move numbers.

SOFTWARE/OS VERSIONS
Linux/KDE Snap package in Ubuntu 18.04

ADDITIONAL INFORMATION
I thought I could use this feature to record games later in SGF manually, but when a big group is captured, it's very hard to reproduce from memory.  I also thought that kigo's internal memory could be used to create an SGF (since using gnugo doesn't record individual moves, just the board position).  But if the move numbers are wrong, that may or may not work.

Comment 1 Glen K. Peterson 2018-11-20 18:57:34 UTC

Created attachment 116430 [details]
Correct move numbers before capture

Comment 2 Glen K. Peterson 2018-11-20 18:58:08 UTC

Created attachment 116431 [details]
Incorrect move numbers after capture

Comment 3 Justin Zobel 2023-01-02 07:43:36 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2023-01-17 05:16:57 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2023-02-01 05:06:11 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!