Bug 228544

Summary: graphic errors on big boards (in terms of pixels)
Product: [Applications] kigo Reporter: Martin <martin.kuettler>
Component: generalAssignee: Sascha Peilicke <saschpe>
Status: RESOLVED WORKSFORME    
Severity: normal CC: heri+kde, kde-games-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Two stones are drawn incorrectly
The same board drawn correctly (after it was covered by another window and repainted)

Description Martin 2010-02-25 23:13:42 UTC
Version:            (using KDE 4.4.0)
Compiler:          gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1 
OS:                Linux
Installed from:    Ubuntu Packages

Both with the ubuntu package and the current svn version I have a graphics error when the board is displayed bigly. For 9x9 board this happens with the default size, 19x19 board are only affected when I maximize the window. In these situations the mouse-cursor (depicting a transparent stone, I could only check this when it's the humans turn) flickers when it is moved, and some stones are only drawn partly, sometimes not at all. How they are drawn exactly seems to change whenever they are redrawn. Moving or resizing the window results in a temporarily well drawn board.
This only happens above a specific (pixel-)size, for me this seems to be approximately 50 pixels from one intersection to an adjacent one.

After a short look at the code I think I might know why the cursor flickers. GameScene::mouseMoveEvent emits a cursorPixmapChanged which changes the cursor, even when this cursor is already set. It might look better when this is only called when the mouse enters the GameScene.

I filed this bug for the ubuntu version, because when I tested the svn version I compiled only the game with kde development packages from ubuntu, and not all of kde.
Comment 1 Martin 2010-02-25 23:47:17 UTC
Changing line 279 of src/gui/graphicsview/gamescene.cpp from
if (m_game->currentPlayer().isHuman()) {
to
if (m_game->currentPlayer().isHuman() && not m_mouseRect.contains(event->lastScenePos())) {
made the mouse cursor flicker perceptibly less, though it still has some minor flaws.
Comment 2 Sascha Peilicke 2010-03-03 18:51:05 UTC
Maybe it's a graphics driver issue? I can't really confirm this behavior under openSUSE (fgrlx and vbox drivers). Which versions of Qt and Kigo do you use?
Comment 3 Martin 2010-03-04 14:30:29 UTC
I am using Kigo version 0.5.5 and Qt from the kubuntu package which says the version is 4.5.3really4.5.2-0ubuntu1. My graphics driver is nvidia, and it seems to work well for the other applications.
I'll attach a screenshot to show what I mean.
Comment 4 Martin 2010-03-04 14:32:26 UTC
Created attachment 41323 [details]
Two stones are drawn incorrectly
Comment 5 Martin 2010-03-04 14:34:47 UTC
Created attachment 41325 [details]
The same board drawn correctly (after it was covered by another window and repainted)
Comment 6 Dennis Schridde 2010-08-03 22:43:12 UTC
Related to bug #241115 and bug #242634?
Comment 7 Andrew Crouthamel 2018-11-05 03:15:32 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-11-17 05:05:41 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Justin Zobel 2022-12-19 00:13:40 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 10 Bug Janitor Service 2023-01-03 05:26:47 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 11 Bug Janitor Service 2023-01-18 05:11:53 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!