After several (many?) levels the newly dealt cards may come in tinted as selected

[MrCsabaToth]

That selection tint is fake because if I select a hand it is still removed, while the fake tinted ones stay. But once this error kicks in the game stays like that and all newly dealt cards became like that.

[MrCsabaToth]

I'm debugging this intensively. Apparently this can happen if the decks in the shoe rotated over completely. Besides the selected cards appearing also empty slots start to appear on the board after a while. The empty slots would be Invalid cards theoretically (a safety measure causes the draw of an empty slot), but in this state the board actually has legitimate cards in the place of the empty slots. So far all my tests and debug couldn't reveal an error on my end.

• If there was a bug with the card removal / insertion logic it'd come earlier.
• I'm pretty sure now that it starts to happen when the shoe is rotated over.
• Everything points to some major internal screw-up inside the AnimatedList.
• What I tried to do besides honing on with deck and shoe tests is to bump the deck index of a deck in the shoe once it's spent and left behind. Later this'd cause the theoretically different state cards to be dealt once the shoe is rotated around, so at least the AnimatedList wouldn't associate to the past by the exact card state. So far this deck index bumping didn't help.
• I assume that the AnimatedList has some internal state which gets messed up big time.

Partial workaround would be to increase the shoe size to a very large number. Given this bug is set off when the shoe is rotated around. Instead of that I'm developing now an endless shoe, which adds new decks on demand instead of rotatng around and recycling a constant finite amount of decks.

[MrCsabaToth]

The bottomless shoe solves the bug. It's a question now if that can consume up too much resources, but doe to the nature of the logarithmic level progression probably players cannot reach a point when the number of dealt decks would cause a real performance issue.

In case this issue will come back in any form, one more change can be made: the y in the listKeys[x].currentState.insertItem(y) stays in the range of [0...maxY - 1] (maxY 4 or 5). If the recurrence of numbers may inflict any bug inside the AnimatedList state internals we can make y a monotonic increasing value: it can index a linear range which can be translated back to deck index and card index within that. Or we can employ an additional dealt card list but probably we can just transform the linear range by the shoe.