Summary: | Golf club is always in the upper left corner | ||
---|---|---|---|
Product: | [Applications] kolf | Reporter: | Jochen <albertjn> |
Component: | general | Assignee: | Jason Katz-Brown <jasonkb> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gfaraway, kde, schwarzer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jochen
2004-02-16 17:59:22 UTC
Update: The golf club is working as expected, only the graphic (signalling of target and power, hope you know what i mean) is fixed in the upper left corner. Im experiencing the problem as well. So I guess the status can be changed to confirmed. The bug report tool gave me the following info, so I guess its important enough to post here. Kolf Version 1.1 OS: Linux (x86_64) release 2.6.3-rc2-gentoo Compiler: gcc version 3.3.2 20040119 (Gentoo Linux 3.3.2-r7, propolice-3.3-7) I have the same problem, systeminfo: Kolf version 1.1 OS: Linux (i686) release 2.4.21-192-default Compiler: gcc version 3.3.1 (SuSE Linux) running SuSE 9.0 with KDE 3.2 I have this same issue here. Would a screenshot help illustrate the situation? What else can we do to assist in tracking down the bug? Kolf 1.1 / KDE 3.2.1 Linux 2.4.22-gentoo-r7 gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7) I'll look into this while I'm back at home soon. thanks for all the comments everybody, i've never seen it but will try to reproduce. In game.cpp Putter::moveBy, guildeLine->move(x(), y()) is always being called with 0,0. In other words, the QCanvasLine::moveBy(dx, dy) doesn't seem to be working properly. (?) Qt bug? I'm using 3.3.0-r1. Installed qt-3.3.1-r2 and the problem went away. It looks like the version of qt I was using was bad, bad, bad. (BTW, the -r1 and -r2 are Gentoo additives to the version. Sorry I forgot to mention that...) Can the other pleople confirm that upgrading qt fixes the problem? Upgrading QT worked for me. Fixed years ago (qt bug) -> fix confirmed -> case closed :) *** Bug 76972 has been marked as a duplicate of this bug. *** |