Bug 343587 - Several UX issues
Summary: Several UX issues
Status: RESOLVED NOT A BUG
Alias: None
Product: kigo
Classification: Applications
Component: general (other bugs)
Version First Reported In: 0.5.6
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Sascha Peilicke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-30 20:19 UTC by Roland Illig
Modified: 2026-01-27 20:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Illig 2015-01-30 20:19:57 UTC
* when I move the mouse over the board, the mouse cursor changes into a black or white stone. This stone doesn’t snap in at the grid, but follows the mouse smoothly. This irritates me, since stones can only be placed on the intersections, not arbitrarily. Therefore the stone should snap to the grid, while the little dot should move smoothly.

* during play, the last played stone should be marked specially. This is usual for go programs, so kigo should do the same. It distracts me from the game when I have to lookup the coordinates in the game protocol to find them on the board.

* after playing the moves, when both players have passed, I can still click on the Pass Move button indefinitely, alternatingly passing for Black and White. This should not be possible.

* the Finish Game button confuses me. Normally the game automatically switches into a mode where both players can mark stones as dead or alive. Kigo doesn’t do this. 

* when I press the Finish Game button, the UI freezes for several seconds. There should be some activity indicator saying that the final score is computed.

* when showing the final result, it is not immediately clear which stones are captured. In other programs they are crossed out or have a pale color. In Kigo they look like the alive stones.


Reproducible: Always
Comment 1 Justin Zobel 2021-03-09 23:51:15 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 2 aristsakas 2026-01-27 20:31:53 UTC
Thanks for the bug report! Unfortunately it reports multiple distinct issues, which will make it not actionable. See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more explanation.
Can I ask you to submit a new bug report for each specific issue? Thanks again!