1,316
edits
m (Edits link) |
Praetorian (talk | contribs) (→Additional Feature: Minor spelling correction) |
||
Line 18: | 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 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 | 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 set the '''kFeatureDisableKeyFiltering''' feature to true. Respectively, when it closes, it sets it to false. By observing this feature, the backends can allocate a flag which indicates when it would be best to suppress mapping from the numeric (and *, #) keys to actions. |
edits