Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
A swipe keyboard with good prediction would be the fastest touch input for me, that would be nice to have too.
Also, would preset strings not be a function of the onscreen keyboard? Mobile keyboards have a user dictionary setting for this purpose.
I'd argue against it. The point of this is to make inputting quick canned responses very quick for times you don't have time to properly type out a command. Having to bring up the keyboard, navigate to the correct place, select the option in the user dictionary and then close the keyboard would make this much longer, though it would still be better than typing manually.
Though if you could send a command to the onscreen keyboard via the bindings menu without having to bring it up, that works fine too
H (start press)
E sub command
L sub command
L ( start press) extra command + fire start delay (50)
O sub command
space sub command
W sub command
O (start press) extra command + fire start delay (100)
R sub command
L sub command
D sub command
It would be less time consuming binding a string.
- We can't write a character that is not present on the keyboard, only ASCII
- We can't write repeated characters fast (e.g. a 10ms delay is not enough)
- Sometimes repeated characters are not typed correctly