Difference between revisions of "AGI/Predictive Dialog"

AGI/Predictive Dialog (view source)

Revision as of 16:19, 10 June 2007

160 bytes added , 16:19, 10 June 2007

Added info about the pred.dic file, fixed a typo

Md5

1,489

edits

@@ 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.
+In order to enable predictive input in AGI games, you need to copy the pred.dic file in the ScummVM extras folder or the folder of the game you wish to play.
 == Input Methods ==
@@ Line 16: / Line 18: @@
 == 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 Prdictive 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.
+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.