| Summary: | Cannot See What Computer's Last Move Was If Visual Cue Missed ... | ||
|---|---|---|---|
| Product: | [Applications] KSquares | Reporter: | Fred <ServaLan> |
| Component: | general | Assignee: | Matt Williams <matt> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | kde-games-bugs-null, vbhunt |
| Priority: | NOR | ||
| Version First Reported In: | 0.6.240480 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Fred
2018-11-11 19:15:20 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! 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! 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! (In reply to Justin Zobel from comment #1) > 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! You took 4 years to reply to this bug. The guy probably doesn't even use KDE any more because of the recent batch of bugs that started when KDE 6 hit. Yes, the bug is still there (I just tried it on a 40x20 board) and it's as annoying as hell. The issue is that there is no way to show a replay of the computer's move and the computer moves so fast that it isn't even comparable to playing a human in the game on paper. If you blink, you miss the computer's move and good luck sussing it out in the early stages of a 40x20 (or larger) game. A simple solution would to let the blinking of the computer's move continue for about 10-15 seconds (or even until the human moves). A more KDE-style solution would be to have a hint button or replay button that would blink the last move while pressed by the user in case the user. Reopening this rather than opening a new bug report on it. It's a logic bug on how the game is designed to work, not a programming bug that causes the game to crash or anything. To fix this bug, you either need to add a feature or change how long the last move is hard-coded to flash. I don't have access to change the severity of this bug, but this could easily be classified as "wish list" level severity. An alternate solution is to make the time that the computer's move blinks configurable in a settings dialog. This is perhaps the most KDE-like solution to this bug. I'd start by looking at line 25 in KSqaures/src/highlightanimation.cpp. |