HomeSort by relevance Sort by last modified time
    Searched full:invisible (Results 601 - 625 of 1223) sorted by null

<<21222324252627282930>>

  /packages/apps/Launcher3/src/com/android/launcher3/
LauncherClings.java 190 // To catch cases where siblings of top-level views are made invisible, just check whether
  /packages/apps/Protips/src/com/android/protips/
ProtipWidget.java 241 updateViews.setViewVisibility(R.id.tip_bubble, View.INVISIBLE);
  /packages/apps/TvSettings/Settings/src/com/android/tv/settings/system/
CaptionPreviewFragment.java 302 mPreviewText.setVisibility(View.INVISIBLE);
  /packages/apps/UnifiedEmail/res/menu-sw600dp-land/
conversation_actions.xml 141 <!-- These invisible menu items are used to enable keyboard shortcuts -->
  /packages/apps/UnifiedEmail/src/com/android/mail/ui/
AttachmentTile.java 111 setVisibility(View.INVISIBLE);
MaterialSearchViewController.java 141 drawerOpen ? View.INVISIBLE : defaultVisibility);
  /packages/services/Telephony/src/com/android/phone/
InCallScreenShowActivation.java 34 * Invisible activity that handles the com.android.phone.PERFORM_CDMA_PROVISIONING intent.
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/sysroot/usr/include/
cursesp.h 141 // Hide the panel. It stays in the stack but becomes invisible.
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/sysroot/usr/include/
cursesp.h 141 // Hide the panel. It stays in the stack but becomes invisible.
  /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/lib-tk/
tkSimpleDialog.py 49 self.withdraw() # remain invisible for now
  /prebuilts/python/linux-x86/2.7.5/lib/python2.7/lib-tk/
tkSimpleDialog.py 49 self.withdraw() # remain invisible for now
  /cts/tools/dasm/src/dasm/
parser.cup 69 TO, INNER, OUTER, VISIBLE, INVISIBLE, VISIBLEPARAM, INVISIBLEPARAM,
323 INVISIBLE classname:name SEP
332 INVISIBLE classname:name SEP
  /external/chromium_org/chrome/browser/chromeos/system/
tray_accessibility_browsertest.cc 285 // Confirms that the icon is invisible before login.
292 // Confirms that the icon is invisible just after login.
491 // Confirms that the menu is invisible.
    [all...]
  /external/chromium_org/chrome/browser/ui/cocoa/tabs/
tab_strip_drag_controller.mm 479 // Sets whether the window background should be visible or invisible when
480 // dragging a tab. The background should be invisible when the mouse is over a
491 // translucent or invisible. As a result, don't animate the alpha change.
  /external/chromium_org/native_client_sdk/doc_generated/pepper_beta/c/
struct_p_p_b___view__1__1.html 43 <p>Note that painting of the page and sending of view changed updates happens asynchronously. This means when the user scrolls, for example, it is likely that the previous backing store of the module instance will be used for the first paint, and will be updated later when your application generates new content with the new clip. This may cause flickering at the boundaries when scrolling. If you do choose to do partial updates, you may want to think about what color the invisible portions of your backing store contain (be it transparent or some background color) or to paint a certain region outside the clip to reduce the visual distraction when this happens.</p>
152 <p>The most common cause of invisible pages is that the page is in a background tab in the browser.</p>
196 <p>Use the result to speed up or stop updates for invisible module instances.</p>
  /external/chromium_org/native_client_sdk/doc_generated/pepper_beta/cpp/
classpp_1_1_view.html 89 <p>Note that painting of the page and sending of view changed updates happens asynchronously. This means when the user scrolls, for example, it is likely that the previous backing store of the module instance will be used for the first paint, and will be updated later when your application generates new content with the new clip. This may cause flickering at the boundaries when scrolling. If you do choose to do partial updates, you may want to think about what color the invisible portions of your backing store contain (be it transparent or some background color) or to paint a certain region outside the clip to reduce the visual distraction when this happens.</p>
181 <p>The most common cause of invisible pages is that the page is in a background tab in the browser.</p>
201 <p>Use the result to speed up or stop updates for invisible module instances.</p>
  /external/chromium_org/native_client_sdk/doc_generated/pepper_dev/c/
struct_p_p_b___view__1__2.html 44 <p>Note that painting of the page and sending of view changed updates happens asynchronously. This means when the user scrolls, for example, it is likely that the previous backing store of the module instance will be used for the first paint, and will be updated later when your application generates new content with the new clip. This may cause flickering at the boundaries when scrolling. If you do choose to do partial updates, you may want to think about what color the invisible portions of your backing store contain (be it transparent or some background color) or to paint a certain region outside the clip to reduce the visual distraction when this happens.</p>
174 <p>The most common cause of invisible pages is that the page is in a background tab in the browser.</p>
218 <p>Use the result to speed up or stop updates for invisible module instances.</p>
  /external/chromium_org/native_client_sdk/doc_generated/pepper_dev/cpp/
classpp_1_1_view.html 90 <p>Note that painting of the page and sending of view changed updates happens asynchronously. This means when the user scrolls, for example, it is likely that the previous backing store of the module instance will be used for the first paint, and will be updated later when your application generates new content with the new clip. This may cause flickering at the boundaries when scrolling. If you do choose to do partial updates, you may want to think about what color the invisible portions of your backing store contain (be it transparent or some background color) or to paint a certain region outside the clip to reduce the visual distraction when this happens.</p>
199 <p>The most common cause of invisible pages is that the page is in a background tab in the browser.</p>
219 <p>Use the result to speed up or stop updates for invisible module instances.</p>
  /external/chromium_org/native_client_sdk/doc_generated/pepper_stable/c/
struct_p_p_b___view__1__1.html 43 <p>Note that painting of the page and sending of view changed updates happens asynchronously. This means when the user scrolls, for example, it is likely that the previous backing store of the module instance will be used for the first paint, and will be updated later when your application generates new content with the new clip. This may cause flickering at the boundaries when scrolling. If you do choose to do partial updates, you may want to think about what color the invisible portions of your backing store contain (be it transparent or some background color) or to paint a certain region outside the clip to reduce the visual distraction when this happens.</p>
152 <p>The most common cause of invisible pages is that the page is in a background tab in the browser.</p>
196 <p>Use the result to speed up or stop updates for invisible module instances.</p>
  /external/chromium_org/native_client_sdk/doc_generated/pepper_stable/cpp/
classpp_1_1_view.html 89 <p>Note that painting of the page and sending of view changed updates happens asynchronously. This means when the user scrolls, for example, it is likely that the previous backing store of the module instance will be used for the first paint, and will be updated later when your application generates new content with the new clip. This may cause flickering at the boundaries when scrolling. If you do choose to do partial updates, you may want to think about what color the invisible portions of your backing store contain (be it transparent or some background color) or to paint a certain region outside the clip to reduce the visual distraction when this happens.</p>
181 <p>The most common cause of invisible pages is that the page is in a background tab in the browser.</p>
201 <p>Use the result to speed up or stop updates for invisible module instances.</p>
  /external/chromium_org/third_party/libjingle/source/talk/examples/android/src/org/appspot/apprtc/
AppRTCDemoActivity.java 132 hudView.setVisibility(View.INVISIBLE);
185 hudView.setVisibility(View.INVISIBLE);
305 if (hudView.getVisibility() == View.INVISIBLE) {
  /external/deqp/modules/gles3/functional/
es3fOcclusionQueryTests.cpp 52 // Constants to tweak visible/invisible case probability balance.
408 log << tcu::TestLog::Message << "Occlusion query result: Target " << (queryResult ? "visible" : "invisible") << "\n"
409 << "Framebuffer read result: Target " << (colorReadResult ? "visible" : "invisible") << tcu::TestLog::EndMessage;
  /frameworks/base/core/java/android/transition/
Visibility.java 217 // no visibilityChange if going between INVISIBLE and GONE
328 * If a visible View is changed to be {@link View#GONE} or {@link View#INVISIBLE},
395 if (endVisibility == View.INVISIBLE) {
  /frameworks/base/core/java/android/widget/
FrameLayout.java 642 * the VISIBLE or INVISIBLE state, when measuring. Defaults to false.
656 * INVISIBLE state, are considered when measuring.
672 * INVISIBLE state, are considered when measuring.
  /frameworks/base/packages/SystemUI/src/com/android/systemui/recent/
RecentsPanelView.java 234 holder.iconView.setVisibility(INVISIBLE);
241 holder.thumbnailView.setVisibility(INVISIBLE);
342 mRecentsNoApps.setVisibility(noApps ? View.VISIBLE : View.INVISIBLE);
    [all...]

Completed in 1107 milliseconds

<<21222324252627282930>>