java.lang.Object | |||||
↳ | android.content.Context | ||||
↳ | android.content.ContextWrapper | ||||
↳ | android.app.Service | ||||
↳ | android.inputmethodservice.AbstractInputMethodService | ||||
↳ | android.inputmethodservice.InputMethodService |
InputMethodService provides a standard implementation of an InputMethod, which final implementations can derive from and customize. See the base class AbstractInputMethodService and the InputMethod interface for more information on the basics of writing input methods.
In addition to the normal Service lifecycle methods, this class introduces some new specific callbacks that most subclasses will want to make use of:
An input method has significant discretion in how it goes about its work: the InputMethodService provides a basic framework for standard UI elements (input view, candidates view, and running in fullscreen mode), but it is up to a particular implementor to decide how to use them. For example, one input method could implement an input area with a keyboard, another could allow the user to draw text, while a third could have no input area (and thus not be visible to the user) but instead listen to audio and perform text to speech conversion.
In the implementation provided here, all of these elements are placed together in a single window managed by the InputMethodService. It will execute callbacks as it needs information about them, and provides APIs for programmatic control over them. They layout of these elements is explicitly defined:
Central to most input methods is the soft input view. This is where most user interaction occurs: pressing on soft keys, drawing characters, or however else your input method wants to generate text. Most implementations will simply have their own view doing all of this work, and return a new instance of it when onCreateInputView() is called. At that point, as long as the input view is visible, you will see user interaction in that view and can call back on the InputMethodService to interact with the application as appropriate.
There are some situations where you want to decide whether or not your soft input view should be shown to the user. This is done by implementing the onEvaluateInputViewShown() to return true or false based on whether it should be shown in the current environment. If any of your state has changed that may impact this, call updateInputViewShown() to have it re-evaluated. The default implementation always shows the input view unless there is a hard keyboard available, which is the appropriate behavior for most input methods.
Often while the user is generating raw text, an input method wants to provide them with a list of possible interpretations of that text that can be selected for use. This is accomplished with the candidates view, and like the soft input view you implement onCreateCandidatesView() to instantiate your own view implementing your candidates UI.
Management of the candidates view is a little different than the input view, because the candidates view tends to be more transient, being shown only when there are possible candidates for the current text being entered by the user. To control whether the candidates view is shown, you use setCandidatesViewShown(boolean). Note that because the candidate view tends to be shown and hidden a lot, it does not impact the application UI in the same way as the soft input view: it will never cause application windows to resize, only cause them to be panned if needed for the user to see the current focus.
Sometimes your input method UI is too large to integrate with the application UI, so you just want to take over the screen. This is accomplished by switching to full-screen mode, causing the input method window to fill the entire screen and add its own "extracted text" editor showing the user the text that is being typed. Unlike the other UI elements, there is a standard implementation for the extract editor that you should not need to change. The editor is placed at the top of the IME, above the input and candidates views.
Similar to the input view, you control whether the IME is running in fullscreen mode by implementing onEvaluateFullscreenMode() to return true or false based on whether it should be fullscreen in the current environment. If any of your state has changed that may impact this, call updateFullscreenMode() to have it re-evaluated. The default implementation selects fullscreen mode when the screen is in a landscape orientation, which is appropriate behavior for most input methods that have a significant input area.
When in fullscreen mode, you have some special requirements because the user can not see the application UI. In particular, you should implement onDisplayCompletions(CompletionInfo[]) to show completions generated by your application, typically in your candidates view like you would normally show candidates.
The key part of an IME is of course generating text for the application. This is done through calls to the InputConnection interface to the application, which can be retrieved from getCurrentInputConnection(). This interface allows you to generate raw key events or, if the target supports it, directly edit in strings of candidates and committed text.
Information about what the target is expected and supports can be found through the EditorInfo class, which is retrieved with getCurrentInputEditorInfo() method. The most important part of this is EditorInfo.inputType; in particular, if this is EditorInfo.TYPE_NULL, then the target does not support complex edits and you need to only deliver raw key events to it. An input method will also want to look at other values here, to for example detect password mode, auto complete text views, phone number entry, etc.
When the user switches between input targets, you will receive calls to onFinishInput() and onStartInput(EditorInfo, boolean). You can use these to reset and initialize your input state for the current target. For example, you will often want to clear any input state, and update a soft keyboard to be appropriate for the new inputType.
Nested Classes | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
InputMethodService.InputMethodImpl | Concrete implementation of AbstractInputMethodService.AbstractInputMethodImpl that provides all of the standard behavior for an input method. | ||||||||||
InputMethodService.InputMethodSessionImpl | Concrete implementation of AbstractInputMethodService.AbstractInputMethodSessionImpl that provides all of the standard behavior for an input method session. | ||||||||||
InputMethodService.Insets | Information about where interesting parts of the input method UI appear. |
XML Attributes | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
android:imeExtractEnterAnimation | Animation to use when showing the fullscreen extract UI after it had previously been hidden. | ||||||||||
android:imeExtractExitAnimation | Animation to use when hiding the fullscreen extract UI after it had previously been shown. | ||||||||||
android:imeFullscreenBackground | Background to use for entire input method when it is being shown in fullscreen mode with the extract view, to ensure that it completely covers the application. |
[Expand]
Inherited Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
android.content.Context
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Returns the visibility mode (either View.INVISIBLE
or View.GONE) of the candidates view when it is not
shown.
| |||||||||||
Return the currently active InputBinding for the input method, or
null if there is none.
| |||||||||||
Retrieve the currently active InputConnection that is bound to
the input method, or null if there is none.
| |||||||||||
Return the maximum width, in pixels, available the input method.
| |||||||||||
Return text that can be used as a button label for the given
EditorInfo.imeOptions.
| |||||||||||
Return whether the fullscreen extract view is shown.
| |||||||||||
Return whether the input method is currently running in
fullscreen mode.
| |||||||||||
Return whether the soft input view is currently shown to the
user.
| |||||||||||
Returns true if we have been asked to show our input view.
| |||||||||||
Called when a new client has bound to the input method.
| |||||||||||
Compute the interesting insets into your UI.
| |||||||||||
Take care of handling configuration changes.
| |||||||||||
Update the given window's parameters for the given mode.
| |||||||||||
Called by the system when the service is first created.
| |||||||||||
Create and return the view hierarchy used to show candidates.
| |||||||||||
Called by the framework to create the layout for showing extacted text.
| |||||||||||
Implement to return our standard InputMethodService.InputMethodImpl.
| |||||||||||
Implement to return our standard InputMethodService.InputMethodSessionImpl.
| |||||||||||
Create and return the view hierarchy used for the input area (such as
a soft keyboard).
| |||||||||||
Called by the system to notify a Service that it is no longer used and is being removed.
| |||||||||||
Called when the application has reported auto-completion candidates that
it would like to have the input method displayed.
| |||||||||||
Override this to control when the input method should run in
fullscreen mode.
| |||||||||||
Override this to control when the soft input area should be shown to
the user.
| |||||||||||
This is called when the user has selected a context menu item from the
extracted text view, when running in fullscreen mode.
| |||||||||||
This is called when the user has performed a cursor movement in the
extracted text view, when it is running in fullscreen mode.
| |||||||||||
This is called when the user has moved the cursor in the extracted
text view, when running in fullsreen mode.
| |||||||||||
This is called when the user has clicked on the extracted text view,
when running in fullscreen mode.
| |||||||||||
This is called when, while currently displayed in extract mode, the
current input target changes.
| |||||||||||
Called when the candidates view is being hidden from the user.
| |||||||||||
Called to inform the input method that text input has finished in
the last editor.
| |||||||||||
Called when the input view is being hidden from the user.
| |||||||||||
This is a hook that subclasses can use to perform initialization of
their interface.
| |||||||||||
Override this to intercept key down events before they are processed by the
application.
| |||||||||||
Override this to intercept special key multiple events before they are
processed by the
application.
| |||||||||||
Override this to intercept key up events before they are processed by the
application.
| |||||||||||
The system has decided that it may be time to show your input method.
| |||||||||||
Called when only the candidates view has been shown for showing
processing as the user enters text through a hard keyboard.
| |||||||||||
Called to inform the input method that text input has started in an
editor.
| |||||||||||
Called when the input view is being shown and input has started on
a new editor.
| |||||||||||
Called when the previous bound client is no longer associated
with the input method.
| |||||||||||
Called when the application has reported a new location of its text
cursor.
| |||||||||||
Called when the application has reported new extracted text to be shown
due to changes in its current text state.
| |||||||||||
Called when the fullscreen-mode extracting editor info has changed,
to update the state of its UI such as the action buttons shown.
| |||||||||||
Called when the fullscreen-mode extracting editor info has changed,
to determine whether the extracting (extract text and candidates) portion
of the UI should be shown.
| |||||||||||
Called when the application has reported a new selection region of
the text.
| |||||||||||
Called when the input method window has been hidden from the user,
after previously being visible.
| |||||||||||
Called when the input method window has been shown to the user, after
previously not being visible.
| |||||||||||
Close this input method's soft input area, removing it from the display.
| |||||||||||
Ask the input target to execute its default action via
InputConnection.performEditorAction().
| |||||||||||
Send the given key event code (as defined by KeyEvent) to the
current input connection is a key down + key up event pair.
| |||||||||||
Send the given UTF-16 character to the current input connection.
| |||||||||||
Replaces the current candidates view with a new one.
| |||||||||||
Controls the visibility of the candidates display area.
| |||||||||||
Controls the visibility of the extracted text area.
| |||||||||||
Replaces the current input view with a new one.
| |||||||||||
You can call this to customize the theme used by your IME's window.
| |||||||||||
Force switch to a new input method, as identified by id.
| |||||||||||
Re-evaluate whether the input method should be running in fullscreen
mode, and update its UI if this has changed since the last time it
was evaluated.
| |||||||||||
Re-evaluate whether the soft input area should currently be shown, and
update its UI if this has changed since the last time it
was evaluated.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Performs a dump of the InputMethodService's internal state.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class android.inputmethodservice.AbstractInputMethodService
| |||||||||||
From class android.app.Service
| |||||||||||
From class android.content.ContextWrapper
| |||||||||||
From class android.content.Context
| |||||||||||
From class java.lang.Object
| |||||||||||
From interface android.content.ComponentCallbacks
| |||||||||||
From interface android.view.KeyEvent.Callback
|
Animation to use when showing the fullscreen extract UI after it had previously been hidden.
Must be a reference to another resource, in the form "@[+][package:]type:name
"
or to a theme attribute in the form "?[package:][type:]name
".
This corresponds to the global attribute resource symbol imeExtractEnterAnimation.
Animation to use when hiding the fullscreen extract UI after it had previously been shown.
Must be a reference to another resource, in the form "@[+][package:]type:name
"
or to a theme attribute in the form "?[package:][type:]name
".
This corresponds to the global attribute resource symbol imeExtractExitAnimation.
Background to use for entire input method when it is being shown in fullscreen mode with the extract view, to ensure that it completely covers the application. This allows, for example, the candidate view to be hidden while in fullscreen mode without having the application show through behind it.
May be a reference to another resource, in the form "@[+][package:]type:name
"
or to a theme attribute in the form "?[package:][type:]name
".
May be a color value, in the form of "#rgb
", "#argb
",
"#rrggbb
", or "#aarrggbb
".
This corresponds to the global attribute resource symbol imeFullscreenBackground.
Returns the visibility mode (either View.INVISIBLE or View.GONE) of the candidates view when it is not shown. The default implementation returns GONE when isExtractViewShown() returns true, otherwise VISIBLE. Be careful if you change this to return GONE in other situations -- if showing or hiding the candidates view causes your window to resize, this can cause temporary drawing artifacts as the resize takes place.
Return the currently active InputBinding for the input method, or null if there is none.
Retrieve the currently active InputConnection that is bound to the input method, or null if there is none.
Return the maximum width, in pixels, available the input method. Input methods are positioned at the bottom of the screen and, unless running in fullscreen, will generally want to be as short as possible so should compute their height based on their contents. However, they can stretch as much as needed horizontally. The function returns to you the maximum amount of space available horizontally, which you can use if needed for UI placement.
In many cases this is not needed, you can just rely on the normal view layout mechanisms to position your views within the full horizontal space given to the input method.
Note that this value can change dynamically, in particular when the screen orientation changes.
Return text that can be used as a button label for the given EditorInfo.imeOptions. Returns null if there is no action requested. Note that there is no guarantee that the returned text will be relatively short, so you probably do not want to use it as text on a soft keyboard key label.
imeOptions | The value from @link EditorInfo#imeOptions EditorInfo.imeOptions}. |
---|
Return whether the fullscreen extract view is shown. This will only return true if isFullscreenMode() returns true, and in that case its value depends on the last call to setExtractViewShown(boolean). This effectively lets you determine if the application window is entirely covered (when this returns true) or if some part of it may be shown (if this returns false, though if isFullscreenMode() returns true in that case then it is probably only a sliver of the application).
Return whether the input method is currently running in fullscreen mode. This is the mode that was last determined and applied by updateFullscreenMode().
Return whether the soft input view is currently shown to the user. This is the state that was last determined and applied by updateInputViewShown().
Returns true if we have been asked to show our input view.
Called when a new client has bound to the input method. This may be followed by a series of onStartInput(EditorInfo, boolean) and onFinishInput() calls as the user navigates through its UI. Upon this call you know that getCurrentInputBinding() and getCurrentInputConnection() return valid objects.
Compute the interesting insets into your UI. The default implementation uses the top of the candidates frame for the visible insets, and the top of the input frame for the content insets. The default touchable insets are TOUCHABLE_INSETS_VISIBLE.
Note that this method is not called when isExtractViewShown() returns true, since in that case the application is left as-is behind the input method and not impacted by anything in its UI.
outInsets | Fill in with the current UI insets. |
---|
Take care of handling configuration changes. Subclasses of InputMethodService generally don't need to deal directly with this on their own; the standard implementation here takes care of regenerating the input method UI as a result of the configuration change, so you can rely on your onCreateInputView() and other methods being called as appropriate due to a configuration change.
When a configuration change does happen, onInitializeInterface() is guaranteed to be called the next time prior to any of the other input or UI creation callbacks. The following will be called immediately depending if appropriate for current state: onStartInput(EditorInfo, boolean) if input is active, and onCreateInputView() and onStartInputView(EditorInfo, boolean) and related appropriate functions if the UI is displayed.
newConfig | The new device configuration. |
---|
Update the given window's parameters for the given mode. This is called when the window is first displayed and each time the fullscreen or candidates only mode changes.
The default implementation makes the layout for the window FILL_PARENT x FILL_PARENT when in fullscreen mode, and FILL_PARENT x WRAP_CONTENT when in non-fullscreen mode.
win | The input method's window. |
---|---|
isFullscreen | If true, the window is running in fullscreen mode and intended to cover the entire application display. |
isCandidatesOnly | If true, the window is only showing the candidates view and none of the rest of its UI. This is mutually exclusive with fullscreen mode. |
Called by the system when the service is first created. Do not call this method directly.
Create and return the view hierarchy used to show candidates. This will be called once, when the candidates are first displayed. You can return null to have no candidates view; the default implementation returns null.
To control when the candidates view is displayed, use setCandidatesViewShown(boolean). To change the candidates view after the first one is created by this function, use setCandidatesView(View).
Called by the framework to create the layout for showing extacted text. Only called when in fullscreen mode. The returned view hierarchy must have an ExtractEditText whose ID is inputExtractEditText.
Implement to return our standard InputMethodService.InputMethodImpl. Subclasses can override to provide their own customized version.
Implement to return our standard InputMethodService.InputMethodSessionImpl. Subclasses can override to provide their own customized version.
Create and return the view hierarchy used for the input area (such as a soft keyboard). This will be called once, when the input area is first displayed. You can return null to have no input area; the default implementation returns null.
To control when the input view is displayed, implement onEvaluateInputViewShown(). To change the input view after the first one is created by this function, use setInputView(View).
Called by the system to notify a Service that it is no longer used and is being removed. The service should clean up an resources it holds (threads, registered receivers, etc) at this point. Upon return, there will be no more calls in to this Service object and it is effectively dead. Do not call this method directly.
Called when the application has reported auto-completion candidates that it would like to have the input method displayed. Typically these are only used when an input method is running in full-screen mode, since otherwise the user can see and interact with the pop-up window of completions shown by the application.
The default implementation here does nothing.
Override this to control when the input method should run in fullscreen mode. The default implementation runs in fullsceen only when the screen is in landscape mode. If you change what this returns, you will need to call updateFullscreenMode() yourself whenever the returned value may have changed to have it re-evaluated and applied.
Override this to control when the soft input area should be shown to the user. The default implementation only shows the input view when there is no hard keyboard or the keyboard is hidden. If you change what this returns, you will need to call updateInputViewShown() yourself whenever the returned value may have changed to have it re-evalauted and applied.
This is called when the user has selected a context menu item from the extracted text view, when running in fullscreen mode. The default implementation sends this action to the current InputConnection's performContextMenuAction(int), for it to be processed in underlying "real" editor. Re-implement this to provide whatever behavior you want.
This is called when the user has performed a cursor movement in the extracted text view, when it is running in fullscreen mode. The default implementation hides the candidates view when a vertical movement happens, but only if the extracted text editor has a vertical scroll bar because its text doesn't fit. Re-implement this to provide whatever behavior you want.
dx | The amount of cursor movement in the x dimension. |
---|---|
dy | The amount of cursor movement in the y dimension. |
This is called when the user has moved the cursor in the extracted text view, when running in fullsreen mode. The default implementation performs the corresponding selection change on the underlying text editor.
This is called when the user has clicked on the extracted text view, when running in fullscreen mode. The default implementation hides the candidates view when this happens, but only if the extracted text editor has a vertical scroll bar because its text doesn't fit. Re-implement this to provide whatever behavior you want.
This is called when, while currently displayed in extract mode, the current input target changes. The default implementation will auto-hide the IME if the new target is not a full editor, since this can be an confusing experience for the user.
Called when the candidates view is being hidden from the user. This will be called either prior to hiding the window, or prior to switching to another target for editing.
The default implementation uses the InputConnection to clear any active composing text; you can override this (not calling the base class implementation) to perform whatever behavior you would like.
finishingInput | If true, onFinishInput() will be called immediately after. |
---|
Called to inform the input method that text input has finished in the last editor. At this point there may be a call to onStartInput(EditorInfo, boolean) to perform input in a new editor, or the input method may be left idle. This method is not called when input restarts in the same editor.
The default implementation uses the InputConnection to clear any active composing text; you can override this (not calling the base class implementation) to perform whatever behavior you would like.
Called when the input view is being hidden from the user. This will be called either prior to hiding the window, or prior to switching to another target for editing.
The default implementation uses the InputConnection to clear any active composing text; you can override this (not calling the base class implementation) to perform whatever behavior you would like.
finishingInput | If true, onFinishInput() will be called immediately after. |
---|
This is a hook that subclasses can use to perform initialization of their interface. It is called for you prior to any of your UI objects being created, both after the service is first created and after a configuration change happens.
Override this to intercept key down events before they are processed by the application. If you return true, the application will not itself process the event. If you return true, the normal application processing will occur as if the IME had not seen the event at all.
The default implementation intercepts KeyEvent.KEYCODE_BACK to hide the current IME UI if it is shown. In additional, in fullscreen mode only, it will consume DPAD movement events to move the cursor in the extracted text view, not allowing them to perform navigation in the underlying application.
Override this to intercept special key multiple events before they are processed by the application. If you return true, the application will not itself process the event. If you return true, the normal application processing will occur as if the IME had not seen the event at all.
The default implementation always returns false, except when in fullscreen mode, where it will consume DPAD movement events to move the cursor in the extracted text view, not allowing them to perform navigation in the underlying application.
Override this to intercept key up events before they are processed by the application. If you return true, the application will not itself process the event. If you return true, the normal application processing will occur as if the IME had not seen the event at all.
The default implementation always returns false, except when in fullscreen mode, where it will consume DPAD movement events to move the cursor in the extracted text view, not allowing them to perform navigation in the underlying application.
The system has decided that it may be time to show your input method. This is called due to a corresponding call to your InputMethod.showSoftInput() method. The default implementation uses onEvaluateInputViewShown(), onEvaluateFullscreenMode(), and the current configuration to decide whether the input view should be shown at this point.
flags | Provides additional information about the show request, as per InputMethod.showSoftInput(). |
---|---|
configChange | This is true if we are re-showing due to a configuration change. |
Called when only the candidates view has been shown for showing processing as the user enters text through a hard keyboard. This will always be called after onStartInput(EditorInfo, boolean), allowing you to do your general setup there and just view-specific setup here. You are guaranteed that onCreateCandidatesView() will have been called some time before this function is called.
Note that this will not be called when the input method is running in full editing mode, and thus receiving onStartInputView(EditorInfo, boolean) to initiate that operation. This is only for the case when candidates are being shown while the input method editor is hidden but wants to show its candidates UI as text is entered through some other mechanism.
info | Description of the type of text being edited. |
---|---|
restarting | Set to true if we are restarting input on the same text field as before. |
Called to inform the input method that text input has started in an editor. You should use this callback to initialize the state of your input to match the state of the editor given to it.
attribute | The attributes of the editor that input is starting in. |
---|---|
restarting | Set to true if input is restarting in the same editor such as because the application has changed the text in the editor. Otherwise will be false, indicating this is a new session with the editor. |
Called when the input view is being shown and input has started on a new editor. This will always be called after onStartInput(EditorInfo, boolean), allowing you to do your general setup there and just view-specific setup here. You are guaranteed that onCreateInputView() will have been called some time before this function is called.
info | Description of the type of text being edited. |
---|---|
restarting | Set to true if we are restarting input on the same text field as before. |
Called when the previous bound client is no longer associated with the input method. After returning getCurrentInputBinding() and getCurrentInputConnection() will no longer return valid objects.
Called when the application has reported a new location of its text cursor. This is only called if explicitly requested by the input method. The default implementation does nothing.
Called when the application has reported new extracted text to be shown due to changes in its current text state. The default implementation here places the new text in the extract edit text, when the input method is running in fullscreen mode.
Called when the fullscreen-mode extracting editor info has changed, to update the state of its UI such as the action buttons shown. You do not need to deal with this if you are using the standard full screen extract UI. If replacing it, you will need to re-implement this to put the appropriate action button in your own UI and handle it, and perform any other changes.
The standard implementation turns on or off its accessory area depending on whether there is an action button, and hides or shows the entire extract area depending on whether it makes sense for the current editor. In particular, a TYPE_NULL or TYPE_TEXT_VARIATION_FILTER input type will turn off the extract area since there is no text to be shown.
Called when the fullscreen-mode extracting editor info has changed, to determine whether the extracting (extract text and candidates) portion of the UI should be shown. The standard implementation hides or shows the extract area depending on whether it makes sense for the current editor. In particular, a TYPE_NULL input type or IME_FLAG_NO_EXTRACT_UI flag will turn off the extract area since there is no text to be shown.
Called when the application has reported a new selection region of the text. This is called whether or not the input method has requested extracted text updates, although if so it will not receive this call if the extracted text has changed as well.
The default implementation takes care of updating the cursor in the extract text, if it is being shown.
Called when the input method window has been hidden from the user, after previously being visible.
Called when the input method window has been shown to the user, after previously not being visible. This is done after all of the UI setup for the window has occurred (creating its views etc).
Close this input method's soft input area, removing it from the display. The input method will continue running, but the user can no longer use it to generate input by touching the screen.
flags | Provides additional operating flags. Currently may be 0 or have the InputMethodManager.HIDE_IMPLICIT_ONLY bit set. |
---|
Ask the input target to execute its default action via InputConnection.performEditorAction().
fromEnterKey | If true, this will be executed as if the user had pressed an enter key on the keyboard, that is it will not be done if the editor has set EditorInfo.IME_FLAG_NO_ENTER_ACTION. If false, the action will be sent regardless of how the editor has set that flag. |
---|
Send the given key event code (as defined by KeyEvent) to the current input connection is a key down + key up event pair. The sent events have KeyEvent.FLAG_SOFT_KEYBOARD set, so that the recipient can identify them as coming from a software input method, and KeyEvent.FLAG_KEEP_TOUCH_MODE, so that they don't impact the current touch mode of the UI.
keyEventCode | The raw key code to send, as defined by KeyEvent. |
---|
Send the given UTF-16 character to the current input connection. Most characters will be delivered simply by calling InputConnection.commitText() with the character; some, however, may be handled different. In particular, the enter character ('\n') will either be delivered as an action code or a raw key event, as appropriate.
charCode | The UTF-16 character code to send. |
---|
Replaces the current candidates view with a new one. You only need to call this when dynamically changing the view; normally, you should implement onCreateCandidatesView() and create your view when first needed by the input method.
Controls the visibility of the candidates display area. By default it is hidden.
Controls the visibility of the extracted text area. This only applies when the input method is in fullscreen mode, and thus showing extracted text. When false, the extracted text will not be shown, allowing some of the application to be seen behind. This is normally set for you by onUpdateExtractingVisibility(EditorInfo). This controls the visibility of both the extracted text and candidate view; the latter since it is not useful if there is no text to see.
Replaces the current input view with a new one. You only need to call this when dynamically changing the view; normally, you should implement onCreateInputView() and create your view when first needed by the input method.
You can call this to customize the theme used by your IME's window. This theme should typically be one that derives from Theme_InputMethod, which is the default theme you will get. This must be set before onCreate(), so you will typically call it in your constructor with the resource ID of your custom theme.
theme | The style resource describing the theme. |
---|
Force switch to a new input method, as identified by id. This input method will be destroyed, and the requested one started on the current input field.
id | Unique identifier of the new input method ot start. |
---|
Re-evaluate whether the input method should be running in fullscreen mode, and update its UI if this has changed since the last time it was evaluated. This will call onEvaluateFullscreenMode() to determine whether it should currently run in fullscreen mode. You can use isFullscreenMode() to determine if the input method is currently running in fullscreen mode.
Re-evaluate whether the soft input area should currently be shown, and update its UI if this has changed since the last time it was evaluated. This will call onEvaluateInputViewShown() to determine whether the input view should currently be shown. You can use isInputViewShown() to determine if the input view is currently shown.
Performs a dump of the InputMethodService's internal state. Override to add your own information to the dump.
fd | The raw file descriptor that the dump is being sent to. |
---|---|
fout | The PrintWriter to which you should dump your state. This will be closed for you after you return. |
args | additional arguments to the dump request. |