A proposed fix for touch input errors

froggerjohn

Problem: When trying to play quickly, a touch operation is often started before the UI has unlocked. At best, this slows down the interface, but it sometimes results in incorrect tile movements if the interface unlocks in the middle of the drag.

For example, touch tile #1, and drag through tiles 2 & 3. UI unlocks in the middle of the drag, while you're over tile #2. If 2->3 is a valid move, this is the one the game will do, but it's not the move the user expected.

Solution: Always track the "down" event, even when the UI is locked. If it's still locked when you release, nothing happens like it does now. But in the scenario above, where the UI unlocks during the drag, you'll have an accurate representation of the intended move.