Quote:
Originally Posted by answer20
Hopefully I've scanned most of the comments .. I want to put something out there since we 'may' be dealing with unknowns.
Might I suggest that when the units are in 'Shuffle' mode that they don't really care what order they are in when placed in the machine ..
1) Shuffle Mode
2) Place deck in machine
3) RNG 'picks' a redistribution pattern of the cards .. 1 goes to 18, 2 goes to 34, 3 goes to 8, 4 goes to 46, 32 goes to 1 ..ect
4) During the redistribution a camera checks the cards, making sure that all, and only one of each, are included in the deck
5) Ready for launch back into play
...
PSS .. Certainly not a code guy .. but wouldn't this require much less programming than determining an order and then spending the time and 'making certain' that the cards are in that specific order?
Actually no. You method requires more coding.
The machine has the code to read a card rank and suit and then place that card in a particular location. We KNOW this code exists as that is what the machine does in shuffle mode.
Now you don't want to do that (but to a different order), so you need different code (at least slightly different) because you want to generate a destination for a card based not on what the card is but based on the order it hit the machine.
Code overlap but still extra code needed to handle the two different modes.
If both modes work the same with (just with different destination order) you need less code. All the mode, shuffle or sort, does is select a different source for the destination. And in you method, you also need two destination sources.