TrustedUser, Bureaucrats, Administrators
442
edits
Difference between revisions of "AGI/Predictive Dialog"
Jump to navigation
Jump to search
m
Edits link
(AGI's predictive input dialog developer notes) |
m (Edits link) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The Predictive Input Dialog is a ScummVM aid for running AGI engines games (which notoriously have command line input) on devices with limited keyboard input. The dialog is fully usable with the mouse, but a few provisions have been made to make its use more comfortable by naturally mapping the functionality to the keypad. | The Predictive Input Dialog is a ScummVM aid for running AGI engines games (which notoriously have command line input) on devices with limited keyboard input. The dialog is fully usable with the mouse, but a few provisions have been made to make its use more comfortable by naturally mapping the functionality to the keypad. | ||
Newer versions of ScummVM come bundled with the files required to enable Predictive Input Dialog, and do not require any additional action. However, if for some reason predictive input is not working, copy the “pred.dic” file from the [https://github.com/scummvm/scummvm/raw/master/dists/pred.dic ScummVM repository] into either the folder with the other game files, or the extra path folder as set in the ScummVM settings. | |||
== Input Methods == | == Input Methods == | ||
| Line 16: | Line 18: | ||
== Additional Feature == | == Additional Feature == | ||
In the case of the WinCE port, the user is free to map Actions to arbitrary keys on the device. This potentially clashes with the | In the case of the WinCE port, the user is free to map Actions to arbitrary keys on the device. This potentially clashes with the Predictive Dialog (or more accurately, its intended use scheme). When the dialog is shown, the backend needs to be notified to turn off any key filtering it is performing (action mapping) so that all numeric keystrokes reach the predictive dialog unspressed. This is accomplished by the following mechanism: When the dialog starts up, it uses OSystem's '''setFeatureState''' to se the '''kFeatureDisableKeyFiltering''' feature to true. Respectively, when it closes it sets it to false. By observing this features, the backends can allocate a flag which indicates when it would be best to suppress mapping from the numeric (and *, #) keys to actions. | ||