You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FB Messenger does not natively support sending messages with OK or ENTER key. However, it may be possible to hack it by doing:
right-right (select the send button)
send OK
left-left (go back to the text field)
Phase 1 (code cleanup):
Add these new functions: InputField.sendKeyPress(int keyCode) and InputField.sendKeyCombo(List<Integer> keyCodes)
Then replace all sendKeyDownUp() calls with sendKeyPress().
Move the current performOK to InputField as well.
Phase 2 (the hack):
Create AppHacks.getOkCombo(String packageName). It will analyze the package name and return the correct combo or simply null
InputField.performOK will use AppHacks.getOkCombo(). If it returns a combo it will pass it to sendKeyCombo() otherwise, it will run the current routine (probably, defaultOKCombo()).
If it turns out there are too many difficulties along the way, just let it be.
The text was updated successfully, but these errors were encountered:
While working on #286 and #353 a much simple AppHacks class emerged, very different from the original idea. Nevertheless, it works just fine and it allows for even broader hacks support.
FB Messenger does not natively support sending messages with OK or ENTER key. However, it may be possible to hack it by doing:
Phase 1 (code cleanup):
InputField.sendKeyPress(int keyCode)
andInputField.sendKeyCombo(List<Integer> keyCodes)
sendKeyDownUp()
calls withsendKeyPress()
.performOK
toInputField
as well.Phase 2 (the hack):
AppHacks.getOkCombo(String packageName)
. It will analyze the package name and return the correct combo or simplynull
InputField.performOK
will useAppHacks.getOkCombo()
. If it returns a combo it will pass it tosendKeyCombo()
otherwise, it will run the current routine (probably,defaultOKCombo()
).If it turns out there are too many difficulties along the way, just let it be.
The text was updated successfully, but these errors were encountered: