HomeSort by relevance Sort by last modified time
    Searched full:cases (Results 1101 - 1125 of 5535) sorted by null

<<41424344454647484950>>

  /external/valgrind/main/memcheck/tests/
sh-mem.c 27 // XXX: should check the error cases for SET/GET_VBITS also
97 // the address space (which would trigger the slow cases in
  /external/webkit/Source/JavaScriptCore/dfg/
DFGSpeculativeJIT.h 169 // FIXME: in cases where we can statically determine we're going to bail out from the speculative
180 // will make conflicting speculations about the same operand). In such cases this
  /external/webkit/Source/JavaScriptCore/tests/mozilla/ecma/Array/
15.4.4.5-2.js 27 This test file tests cases in which the compare function is supplied.
28 In this cases, the sort creates a reverse sort.
  /external/webkit/Source/JavaScriptCore/tests/mozilla/ecma/Expressions/
11.13.2-4.js 112 // boolean cases
116 // object cases
11.13.2-5.js 112 // boolean cases
116 // object cases
  /external/webkit/Source/WebCore/bindings/js/
JSLocationCustom.cpp 82 // such cases when normally the string form of Location would be the URL.
122 // such cases when normally the string form of Location would be the URL.
  /external/webkit/Tools/Scripts/webkitpy/common/system/
logtesting.py 180 # FIXME: Add a clearMessages() method for cases where the caller
245 # FIXME: Add a clearMessages() method for cases where the caller
  /external/webrtc/src/modules/audio_processing/test/
apmtest.m 5 % 'list' Prints a list of cases in the test set, preceded by their
23 % or set to zero, to use all test cases.
  /external/zlib/src/contrib/iostream2/
zstream.h 63 * cases (if errno is zero, the zlib error is Z_MEM_ERROR).
174 * errno can be checked to distinguish two error cases
  /frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm11/vc/m4p10/src/
omxVCM4P10_InterpolateLuma_s.s 36 ;// It is assued that following cases are satisfied before calling this function:
108 ;// Depending on the values of motion vector fractional parts (dx,dy), one out of 16 cases will be processed.
  /frameworks/base/core/java/android/util/
DisplayMetrics.java 46 * appropriate. In most cases (such as using bitmaps in
72 * being scaled up to it should be sufficient for almost all cases.
  /frameworks/base/core/java/android/view/
ViewParent.java 167 * <p>In most cases, a subclass does not need to override this. However, if
188 * <p>In most cases, a subclass does not need to override this. However, if the
  /frameworks/base/docs/html/design/patterns/
help.jd 12 <h3>Don't show unsolicited help, except in very limited cases</h3>
14 <p>In almost all cases, we advise <strong>against</strong> approaches like these because:</p>
pure-android.jd 19 use gradients in their title bars. In some cases, elements may have the same purpose, but are
94 <p>In some cases you might want your app to take advantage of another app's feature set. For
  /frameworks/base/docs/html/tools/help/
proguard.jd 57 needs. The default configuration file only covers general cases, so you most likely have to edit
132 <p>The default <code>proguard.cfg</code> file tries to cover general cases, but you might
  /frameworks/base/docs/html/training/design-navigation/
wireframing.jd 39 <p>First, our second-level screens (<em>Story Category List</em>, <em>Photo List</em>, and <em>Saved Item List</em>) can be grouped together using tabs. Note that we don't necessarily have to use horizontally arranged tabs; in some cases a drop-down list UI element can serve as a suitable replacement, especially on devices with narrow screens such as handsets. We can also group the <em>Saved Photo List</em> and <em>Saved Story List</em> screens together using tabs on handsets, or use multiple vertical content panes on tablets.</p>
71 <p>The easiest and fastest way to get started is to sketch out your screens by hand using paper and pencils. Once you begin sketching, you may uncover practicality issues in your original screen map or decisions on which patterns to use. In some cases, patterns may apply well to a given design problem in theory, but in practice they may break down and cause visual clutter or interactional issues (for example, if there are two rows of tabs on the screen). If that happens, explore other navigation patterns, or variations on chosen patterns, to arrive at a more optimal set of sketches.</p>
  /frameworks/base/media/libdrm/mobile1/include/objmng/
drm_file.h 158 * Returns #DRM_FILE_FAILURE in all other cases, including those where name exists but is neither
175 * In all cases the current position is set to the start of the file.
  /frameworks/support/v4/java/android/support/v4/app/
NavUtils.java 168 * parent are within the same task. If up navigation should cross tasks in some cases, see
194 * as the destination. If up navigation should cross tasks in some cases, see
  /hardware/ti/omap3/omx/system/src/openmax_il/perf/src/
perf_config.c 302 * In all other cases, it is assigned 0.
364 * 'true', the member is assigned 1. In all other cases, it is
  /hardware/ti/omap4xxx/domx/omx_core/inc/
OMX_TI_Common.h 112 * parameter is valid only in cases where
114 * (i.e. UseBuffer cases).
  /libcore/luni/src/main/java/java/lang/
CaseMapper.java 47 // Punt hard cases to ICU4C.
59 // Punt these hard cases.
  /libcore/luni/src/main/java/org/apache/harmony/xnet/provider/jsse/
FileClientSessionCache.java 54 * cases and even just "not accessed in this process" if the filesystem
94 // File.list() will return null in error cases without throwing IOException
  /packages/apps/Email/tests/src/com/android/emailcommon/utility/
TextUtilitiesTests.java 32 // Test the simplest cases
54 // Test the simplest cases
  /packages/apps/Phone/res/layout/
incall_touch_ui.xml 25 In usual cases, one of these is visible at any given moment.
96 views so that they'll be spaced evenly in both cases.
  /packages/apps/Phone/src/com/android/phone/
AnimationUtils.java 133 * visibility is still VISIBLE, although in many cases the UI
255 * some corner cases. See issue 6300562

Completed in 1323 milliseconds

<<41424344454647484950>>