Bug 184596

Summary:	Layout has mismatched tiles
Product:	[Applications] kmahjongg	Reporter:	Ian Wadham <iandw.au>
Component:	general	Assignee:	Mauricio Piacentini <piacentini>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kde-games-bugs
Priority:	NOR
Version:	0.8
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot of mismatched tiles. Mismatched tiles: KMahjongg game 1,738,590,905.

Description Ian Wadham 2009-02-17 08:15:57 UTC

Version:           0.8 (using 4.1.81 (KDE 4.1.81 (KDE 4.2 >= 20081128)), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.22.13-0.3-default

The layout for game 1,329,940,286 has mismatched tiles, making it impossible to win.  The red dragon does not match the 6 and it is impossible to make matching pairs and win.  "Generate solvable games" setting is ON.  Layout was "Default".

Comment 1 Ian Wadham 2009-02-17 08:25:38 UTC

Created attachment 31386 [details]
Screenshot of mismatched tiles.

Comment 2 Ian Wadham 2009-02-17 08:32:48 UTC

Note that the screenshot is using an amended background-color for the tiles in the Classic theme.  Hope you like it.  IMHO it improves clarity and readability.

Comment 3 Mauricio Piacentini 2009-02-17 12:20:07 UTC

Do you remember if you have used the SHUFFLE command while playing this game?

Comment 4 Ian Wadham 2009-02-17 22:06:20 UTC

I do not think so.  I do not even know what shuffle does exactly.  The manual 
just says it shuffles the tiles, but why would you want to?  I just found 
another case of this bug.  Game 1,979,648,349.  I was down to one layer 
containing 22 tiles and found the red dragon was again unmatched, this time 
with the bird (1) being the other unmatched tile.

Comment 5 Ian Wadham 2009-03-17 12:59:23 UTC

Created attachment 32190 [details]
Mismatched tiles: KMahjongg game 1,738,590,905.

Another example of this bug, or possibly bug 184592.  KMahjongg game 1,738,590,905.

Comment 6 Mauricio Piacentini 2009-03-21 03:46:13 UTC


*** This bug has been marked as a duplicate of bug 184592 ***