From 31a8761bfa16c7f8c26df3bd20509e5a64a05a54 Mon Sep 17 00:00:00 2001 From: Helium314 Date: Thu, 29 May 2025 09:32:12 +0200 Subject: [PATCH] don't always use the same coordinate when creating fake ComposedData for a word avoids some sort of cache returning previous suggestions, see GH-1542 --- .../main/java/helium314/keyboard/latin/common/ComposedData.kt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/app/src/main/java/helium314/keyboard/latin/common/ComposedData.kt b/app/src/main/java/helium314/keyboard/latin/common/ComposedData.kt index 159d1b1c7..091c41920 100644 --- a/app/src/main/java/helium314/keyboard/latin/common/ComposedData.kt +++ b/app/src/main/java/helium314/keyboard/latin/common/ComposedData.kt @@ -6,6 +6,7 @@ package helium314.keyboard.latin.common import helium314.keyboard.latin.WordComposer +import kotlin.random.Random /** An immutable class that encapsulates a snapshot of word composition data. */ class ComposedData( @@ -47,7 +48,7 @@ class ComposedData( val codePoints = StringUtils.toCodePointArray(word) val coordinates = CoordinateUtils.newCoordinateArray(codePoints.size) for (i in codePoints.indices) { - CoordinateUtils.setXYInArray(coordinates, i, Constants.NOT_A_COORDINATE, Constants.NOT_A_COORDINATE) + CoordinateUtils.setXYInArray(coordinates, i, Random.nextBits(2), Random.nextBits(2)) } return WordComposer().apply { setComposingWord(codePoints, coordinates) }.composedDataSnapshot }