![]() |
Re: Advanced text entry on Sailfish (Swype or similar)
Quote:
|
Re: Advanced text entry on Sailfish (Swype or similar)
Quote:
Thanks @eber42 for your fabulous work! *) Only one minor issue: German Keyboard works, but OKboard gives a warning that files need an update to new DB format 16 |
Re: Advanced text entry on Sailfish (Swype or similar)
Just working on the Spanish dictionary update to match DB 16 :D
|
Re: Advanced text entry on Sailfish (Swype or similar)
Quote:
|
Re: Advanced text entry on Sailfish (Swype or similar)
Quote:
Edit: I'm using Fairphone 2, so I doubt it's a port specific problem. |
Re: Advanced text entry on Sailfish (Swype or similar)
To the Italian friends: I will compile the new version of the dict in the next few days. I'm waiting for Eber's confirmation that we can proceed.
|
Re: Advanced text entry on Sailfish (Swype or similar)
Thanks for your feedback. Please notice the following issues:
The current implementation is dependent on screen resolution which means it works well only on the original Jolla phone. I have never released the tablet version because of this (it is really awful, and there are a lot of other concerns with tablet usage ...). So Fairphone & Nexus users are probably getting a sub-par user experience. I will try to find another device with phone form factor to test different screen resolutions. I have rushed the 0.6 release somewhat, so documentation & tools for generating third party language files may not be completely up-to-date. I would recommend maintainers for third party languages to wait a few days until this part is fixed. I will try to make the process smoother for the next release :) |
Re: Advanced text entry on Sailfish (Swype or similar)
Quote:
|
Re: Advanced text entry on Sailfish (Swype or similar)
Quote:
|
Re: Advanced text entry on Sailfish (Swype or similar)
Third party language file generation should be OK so you can give it a try. Just grab the last commit and replace your old configuration file with an empty one to use new default settings.
Quote:
About the cause and the solution you have clearly nailed it :) (even if it is a bit more complicated). The plan is just to scale everything internally based on key size for a quick fix. |
| All times are GMT. The time now is 23:46. |
vBulletin® Version 3.8.8