Probléme de mélange dans un pulzze

The new blocks:

and the sample run, including shuffle ...
Sample run 2
(I didn't bother trying to complete this one.)

It cleared up the messages during the shuffle.

So, the only thing I ended up touching in your app was the list comparison test, where I switched it to comparing the text CSV rows of the two lists.

My blocks in the prior post are draggable.

Oui effectivement, j'avais un message qui apparaissait , merci . (On comprend mieux le jeu quand on le teste, c'est pas évident à expliquer) .
C'est bizarre car pour moi , Quand je mélange n'importe quel premier puzzle que je choisi ça fonctionne et quand je choisi un prochain puzzle il ne se mélange plus. avez vous essayé de choisir d'autres puzzles et de mélanger ?
Merci Taifun pour vos suggestions.

Je viens de m'apercevoir que quand je choisis un puzzle, je le mélange et je ne joue pas , ensuite je choisis un autre puzzle, je le mélange et bien là il ne se mélange pas !!! par contre quand je joue au premier puzzle (je le fini) et que je choisis un autre puzzle le bouton mélanger fonctionne, je ne comprends plus rien!!!

I found an inconsistency in the way you represent the neighbors list of a cell.

You generate a fixed length = 4 list of neighboring cells, with blank for impossible cells.
But you never check for blank when doing randomization as a series of interchanges around the void.

Your old procedure:


My replacement:

You also need


to report errors.

I see that you randomize the puzzle by applying pair switches around the item in global variable Grille that holds 'void' instead of an image file name.

That insures there is no worry of generating an impossible puzzle.

I notice there are sequences of actions that can result in there being two empty cells in a shuffle.

This tutorial made in 2015 shuffles a grid of 9 images.

1 Like

I got the puzzle working, and made it expandable for more puzzles without changing any blocks.


TAQUIN.aia (1.2 MB)

New puzzle files in the Media folder should follow the naming conventions of the earlier puzzles, and the new image components for puzzle selection should have picture files following the same naming convention.

A lot of the problems were caused by duplication of code, and lack of separation of functions.

Some global variables needed to be eliminated, to lower the cognitive load of maintaining them.

Some value functions were added to replace them.

je n'avais pas vu toutes ces erreurs, merci pour votre aide et pour le tutoriel.
Je vais regarder tout ça tranquillement

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.