[Xposed Framework Modules] Roughy:
Exi for Swiftkey 1.3.2 release

1.3.2 [ 15.01.2018 ] - Compatibility fixes, size multiplier, emoji vibrate toggle (Stable: 6.7.4.31, Beta: 6.7.5.28) )

Changes in [1.3.2] (Stable: 6.7.4.31, Beta: 6.7.5.28) :

Fixed

- More suggestions and removal of black bars surrounding candidates targeting >6.7.4.31

- Fixed keys being input before swipe in hold-and-swipe modes (Edit: But two-finger gesture totally broken, hotfix incoming)

- Fixed new emoji back button being too small ( >6.7.5.28)

Fixed

- Toggle to enable/disable vibration when inputting emoji (Exi panel only)

- Keyboard size multiplier (Range 0.3 to 3.0)

Changed

- Recent Emoji panel can now be cleared like the other user-created panels

Download:

Exi for Swiftkey on Xposed module repository

Notes:

"There hasn't been any updates since last year", technically.

Thanks to our dedicated translators this release comes with all the supported languages (Russian, French, Brazillian-Portugese, and Polish) fully translated!

They have also finally been accredited in the about section of the config app.

More suggestions & Candidate bar maximize [MENTION=2372897]Psych0t1c20[/MENTION]

This was broken for a while, but wasn't super critical. Removing the black bars on the sides is done in the same bit of code, so that broke too. Just another tiny layout change on Swiftkey's side.

Emoji vibrate [MENTION=4686530]Mohit Ghune[/MENTION] [MENTION=5542240]fgaurano[/MENTION]

Turns out some people don't like this, thus toggle.

Fixed keys being input before swipe in hold-and-swipe modes

So this happened because swiftkey has changed the behavior when you have 2 fingers on the screen.

Before they would simply ignore the second finger I believe, but now any keys it swipes across will be input, while the first finger triggers flow like usual.

If you were using any of the swipe-selection modes that require two fingers and happened to have a swipe threshold high enough that you would swipe across 2 keys before

swipe-selection was triggered, this new behavior would cause the keys to be input. Very annoying. It has been solved by requiring a that any key input events also require an accompanying finger-up event when certain conditions are met. With any luck that fix won't have any unintended side-effects.

Keyboard size multiplier [MENTION=3213471]ahb83[/MENTION] [MENTION=537184]Techvir[/MENTION]

The keyboard size multiplier, found under Settings - misc - Keyboard size Multiplier, allows you to make the keyboard bigger or smaller.

The multiplier allows any value between 0.3 (smaller) and 3.0 (bigger), and applies to the existing size presets.

This means you can change the multiplier, than go back and try the various size presets Swiftkey provides, as the multiplier will be applied to all of them.

On my device, the largest size preset looks like this. It is certainly large, but if I change the keyboard size multiplier to 2.0, it becomes twice as large.

Clear recent emoji [MENTION=7830895]MBDdk[/MENTION]

The recent emoji panel can now be cleared from the menu like the other user-created panels. Beware that the contents of this panel may not always reflect what is seen inside of the keyboard, as the config app doesn't monitor the panel for changes.

Stuff

This was primarily a compatibility update to fix the bugs introduced by changes to Swiftkey, but I threw in some stuff I could do fairly easily.

[MENTION=6204033]X_Hunter[/MENTION] [MENTION=8824612]D4n13£[/MENTION]

Given the number of people who want an android 4..2.x compatible version I suppose I will be getting to that. I was hoping it would be fairly straight forward, but I am unfortunately utilizing a ton of features that were not available pre-kitkat. Supporting kitkat is bad enoug has it is, really.

[MENTION=6204033]X_Hunter[/MENTION]

I was originally going to include some custom keyboard sounds, but there's copyright hurdles and such to deal with. Leaving it to the user makes my life a lot easier.

It should technically support any audio format, but due to mimetype shenanigans I have to hardcode in the formats, leaving us with mp3 and ogg for now.

The playback volume is decided by Swiftkey, and you can tweak it just like you would the volume of the stock soundclips inside of swiftkey config.

[MENTION=4463645]jimbo1qaz[/MENTION]

You can reset the quick-menu panel to default under settings - restore defaults - quick-menu.

You should be able to scroll anywhere except the handle and number on the left side. The drop-down menus should only trigger with a direct tap, not a scrolling drag gesture.

Are you on an older version of android? The support libraries do have some quirks, and it's possible that they are not behaving correctly on older devices.

For both the swipe sensitivity and the quick-menu handles, being able to select round numbers is... not really a concern.

The guides in the quick-menu configuration panel should allow you to position them as close to even as is humanly discernible, and the "aaaa"s displayed when configuring swipe-selection sensitivity are really only to give you some representation of how fast the cursor will move.