Lines Matching defs:view
19 import static android.view.ViewGroup.LayoutParams.MATCH_PARENT;
20 import static android.view.ViewGroup.LayoutParams.WRAP_CONTENT;
42 import android.view.KeyCharacterMap;
43 import android.view.KeyEvent;
44 import android.view.LayoutInflater;
45 import android.view.MotionEvent;
46 import android.view.View;
47 import android.view.ViewGroup;
48 import android.view.ViewTreeObserver;
49 import android.view.Window;
50 import android.view.WindowManager;
51 import android.view.animation.AnimationUtils;
52 import android.view.inputmethod.CompletionInfo;
53 import android.view.inputmethod.EditorInfo;
54 import android.view.inputmethod.ExtractedText;
55 import android.view.inputmethod.ExtractedTextRequest;
56 import android.view.inputmethod.InputBinding;
57 import android.view.inputmethod.InputConnection;
58 import android.view.inputmethod.InputMethod;
59 import android.view.inputmethod.InputMethodManager;
60 import android.view.inputmethod.InputMethodSubtype;
92 * a basic framework for standard UI elements (input view, candidates view,
106 * <li>The soft input view, if available, is placed at the bottom of the
108 * <li>The candidates view, if currently shown, is placed above the soft
109 * input view.
120 * <p>Central to most input methods is the soft input view. This is where most
123 * will simply have their own view doing all of this work, and return a new
125 * as long as the input view is visible, you will see user interaction in
126 * that view and can call back on the InputMethodService to interact with the
130 * soft input view should be shown to the user. This is done by implementing
135 * implementation always shows the input view unless there is a hard
145 * be selected for use. This is accomplished with the candidates view, and
146 * like the soft input view you implement {@link #onCreateCandidatesView()}
147 * to instantiate your own view implementing your candidates UI.</p>
149 * <p>Management of the candidates view is a little different than the input
150 * view, because the candidates view tends to be more transient, being shown
152 * by the user. To control whether the candidates view is shown, you use
154 * view tends to be shown and hidden a lot, it does not impact the application
155 * UI in the same way as the soft input view: it will never cause application
172 * <p>Similar to the input view, you control whether the IME is running in
185 * generated by your application, typically in your candidates view like you
194 * {@link android.view.inputmethod.InputConnection} interface to the
200 * through the {@link android.view.inputmethod.EditorInfo} class, which is
202 * important part of this is {@link android.view.inputmethod.EditorInfo#inputType
204 * {@link android.view.inputmethod.EditorInfo#TYPE_NULL EditorInfo.TYPE_NULL},
826 * view layout mechanisms to position your views within the full horizontal
928 * candidates view and none of the rest of its UI. This is mutually
975 * of both the extracted text and candidate view; the latter since it is
986 * Return whether the fullscreen extract view is shown. This will only
1062 * determine whether the input view should currently be shown. You
1063 * can use {@link #isInputViewShown()} to determine if the input view
1082 * Returns true if we have been asked to show our input view.
1089 * Return whether the soft input view is <em>currently</em> shown to the
1099 * the user. The default implementation only shows the input view when
1118 // If we are being asked to show the candidates view while the app
1119 // has not asked for the input view to be shown, then we need
1139 * or {@link View#GONE View.GONE}) of the candidates view when it is not
1143 * other situations -- if showing or hiding the candidates view causes
1172 public void setExtractView(View view) {
1174 mExtractFrame.addView(view, new FrameLayout.LayoutParams(
1177 mExtractView = view;
1178 if (view != null) {
1179 mExtractEditText = (ExtractEditText)view.findViewById(
1182 mExtractAction = (Button)view.findViewById(
1185 mExtractAccessories = (ViewGroup)view.findViewById(
1197 * Replaces the current candidates view with a new one. You only need to
1198 * call this when dynamically changing the view; normally, you should
1199 * implement {@link #onCreateCandidatesView()} and create your view when
1202 public void setCandidatesView(View view) {
1204 mCandidatesFrame.addView(view, new FrameLayout.LayoutParams(
1210 * Replaces the current input view with a new one. You only need to
1211 * call this when dynamically changing the view; normally, you should
1212 * implement {@link #onCreateInputView()} and create your view when
1215 public void setInputView(View view) {
1217 mInputFrame.addView(view, new FrameLayout.LayoutParams(
1220 mInputView = view;
1225 * Only called when in fullscreen mode. The returned view hierarchy must
1235 * Create and return the view hierarchy used to show candidates. This will
1237 * null to have no candidates view; the default implementation returns null.
1239 * <p>To control when the candidates view is displayed, use
1241 * To change the candidates view after the first one is created by this
1249 * Create and return the view hierarchy used for the input area (such as
1254 * <p>To control when the input view is displayed, implement
1256 * To change the input view after the first one is created by this
1264 * Called when the input view is being shown and input has started on
1266 * allowing you to do your general setup there and just view-specific
1279 * Called when the input view is being hidden from the user. This will
1301 * Called when only the candidates view has been shown for showing
1304 * allowing you to do your general setup there and just view-specific
1324 * Called when the candidates view is being hidden from the user. This will
1351 * and the current configuration to decide whether the input view should
1668 * Called when the user tapped or clicked a text view.
1672 * @param focusChanged true if the user changed the focused view by this click.
1749 * events to move the cursor in the extracted text view, not allowing
1781 * events to move the cursor in the extracted text view, not allowing
1797 * events to move the cursor in the extracted text view, not allowing
1942 * {@link android.view.inputmethod.InputConnection#commitText} family of methods
2033 * text view, when running in fullsreen mode. The default implementation
2083 * This is called when the user has clicked on the extracted text view,
2085 * the candidates view when this happens, but only if the extracted text
2100 * extracted text view, when it is running in fullscreen mode. The default
2101 * implementation hides the candidates view when a vertical movement
2119 * extracted text view, when running in fullscreen mode. The default