From kde-release-team Sat Jun 27 17:52:43 2009 From: Stefan Majewsky Date: Sat, 27 Jun 2009 17:52:43 +0000 To: kde-release-team Subject: Fwd: [Kde-games-devel] Possibly release-blocking issue for 4.3 (was: Message-Id: <200906271952.43399.majewsky () gmx ! net> X-MARC-Message: https://marc.info/?l=kde-release-team&m=124618813400551 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1455603542==" --===============1455603542== Content-Type: multipart/signed; boundary="nextPart1684172.ZScyMR6f40"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1684172.ZScyMR6f40 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, aacid suggested that this might be of interest for you, too. Greetings Stefan =2D--------- Forwarded message ---------- Subject: [Kde-games-devel] Possibly release-blocking issue for 4.3 (was: Re= :=20 Problems with Kolf) Date: Saturday 27 June 2009 =46rom: Stefan Majewsky To: kde-games-devel@kde.org Cc: kde-devel@kde.org, kde-core-devel@kde.org Okay, now that I've got you're attention: Am Freitag 26 Juni 2009 20:08:06 schrieb Johannes Obermayr: > After I updated my father's KDE from 4.2.4 to 4.2.92 I noticed that in > every course only the first hole is animated correctly. In 4.2.4 it was > ok... > [...] > So I tested it with my laptop (OpenSuSE factory) and my "main" computer > (KDE 4.2.93) and saw that there is the same bug. > > Here are "ksnapshots" from "Slope Practise": > http://www.freeimagehosting.net/uploads/b1c835a07f.png > http://www.freeimagehosting.net/uploads/7a67a9829d.png > http://www.freeimagehosting.net/uploads/59ffb2d1d0.png > > I created also an own course with 3 holes and some items and there is the > same... I'm taking this to k-c-d and k-d. Kolf 1.9 has no maintainer at the moment,= =20 and its source is a complete mess. This means we have only one chance: find= =20 someone who knows about a change in QGraphicsView from 4.4 to 4.5 that migh= t=20 be causing this problem. In this case, someone might be able to hack a fix= =20 together. (I'm well aware that "someone" would most probably translate to=20 "me", as I'm kind of the upcoming Kolf maintainer.) If this is not possible, I'm quite sure no one can/wants to/will waste his= =20 time to dig into the Kolf 1.9 source and find the problem. This would=20 effectively mean to remove Kolf from branches/4.3, and probably also trunk. Greetings Stefan =2D------------------------------------------------------------ --nextPart1684172.ZScyMR6f40 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkpGXGsACgkQ3trDvSmezKi3XACbBzmr1vd25N59i/ieCkmrOu3i l9IAoJSsEa2iJUNFeLlTJQS5x1MkPCPW =J6wo -----END PGP SIGNATURE----- --nextPart1684172.ZScyMR6f40-- --===============1455603542== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team --===============1455603542==--