This repository has been archived by the owner on Jan 13, 2023. It is now read-only.
A bit more feature overhaul and bug fixes #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 9 commits
February 22, 2021 08:14
…d assign max priority to newly added word
|
Hey, @vladkorotnev , did you make any configuration changes to make the project build on newer versions of Android Studio or you are just using an old version? Your changes look ok and I want to use them as a base for adding a new language, but I am still struggling at the start... |
|
I don’t think I did, even if anything it was something Android Studio suggested on its own. And I was using the latest at the time. |
|
I see. Well, it seems some things have changed in the meantime, so I guess I have to figure them out on my own. Thanks anyway! |
|
Some user in the Qin F21 Pro telegram group compiled a bunch of versions
with different languages. I downloaded a Norwegian version off there. Guess
you could reach out there. Her username is @susxel and the group is:
https://t.me/f21pro
…On Sat, Jun 11, 2022 at 2:11 PM Dimo Karaivanov ***@***.***> wrote:
I see. Well, it seems some things have changed in the meantime, so I guess
I have to figure them out on my own. Thanks anyway!
—
Reply to this email directly, view it on GitHub
<https://github.com/Clam-/TraditionalT9/pull/31#issuecomment-1152912917>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APAX2I7TL4KQHXUSYTP3LVLVOR66LANCNFSM4YAROT7A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please review this in detail as I've changed the database so maybe it has breaking changes.
Changed things:
Detailed explanation of "Intelligent frequency updating":
Old algorithm used to increment frequency each time the word is chosen. If the frequency went past 10000 then all frequencies for that key sequence will be divided by 10000. That would cause problems if you have a VERY popular word and some less popular words on the same sequence — if you type in the VERY popular one 10000+ times, order of all others will mess up.
New algorithm brings the chosen word to the top, if it's not the topmost, then does nothing. This also helps to deal with a preheated dictionary having a bunch of nonsense with a bigger frequency than what you wanted to type.
I've used this now for a few minutes and it's as comfortable as my old Nokias were (or how I remember them) :-)