HomeSort by relevance Sort by last modified time
    Searched full:changes (Results 351 - 375 of 16558) sorted by null

<<11121314151617181920>>

  /sdk/testapps/javaProjectTest/lib2/
project.properties 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
  /sdk/testapps/legacyTest/
project.properties 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
  /sdk/testapps/libsTest/lib2/
project.properties 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
  /sdk/testapps/testProjectTest/lib/
project.properties 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
  /sdk/testapps/userLibTest/
project.properties 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
  /system/chre/external/flatbuffers/
README.md 4 changes described in the comment at the top of flatbuffers.h, and apply them to
  /system/tools/aidl/docs/
making-changes.md 1 # Making changes
  /packages/apps/Settings/
color-check-baseline.xml 11 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
27 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
43 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
59 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
75 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
91 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
107 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
123 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
139 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColorPrimary` in attributes.&#xA;This ensures that a theme change from a light to a dark theme can be uniformlyapplied across the app."
155 explanation="Hardcoded color values are bad because theme changes cannot be uniformly applied.Instead use the theme specific colors such as `?android:attr/textColor (…)
    [all...]
  /external/mesa3d/docs/
repository.html 176 <li>Small changes to master
182 But for small changes to the master branch itself,
195 Make your changes and use
201 to get your changes ready to push back into the fd.o repository.
205 you did your last pull. Even if your changes do not conflict with
206 their changes, git will make a fast-forward
208 where you did your last pull and merging it to a point after the other changes.
223 In any case, your repository now looks like you made your changes after
224 all the other changes.
227 If the rebase resulted in conflicts or changes that could affec
    [all...]
  /system/update_engine/update_manager/
variable.h 34 // whether, how and when the value of the variable changes.
36 // Const variables never changes during the life of a policy request, so the
43 // changes on the source of information. In order to detect if the value of
44 // the variable changes, it has to be queried again.
48 // value changes. This means that it's not required to poll the value to
49 // detect when it changes, instead, you should register an observer to get
58 // Interface for observing changes on variable value.
63 // Called when the value on the variable changes.
92 // Adds and removes observers for value changes on the variable. This only
94 // changes. Adding the same observer twice has no effect
    [all...]
  /external/tagsoup/
CHANGES 0 Changes from 1.2 to 1.2.1
7 Changes from 1.1.3 to 1.2
32 Changes from 1.1.2 to 1.1.3
38 Changes from 1.1.1 to 1.1.2
42 Changes from 1.1 to 1.1.1
48 Changes from 1.0.5 to 1.1
52 Changes from 1.0.4 to 1.0.5
60 Changes from 1.0.4 to 1.0.3
66 Changes from 1.0.3 to 1.0.2
71 Changes from 1.0.1 to 1.0.
    [all...]
  /frameworks/base/telephony/java/android/telephony/
PhoneStateListener.java 31 * A listener class for monitoring changes in specific telephony states
55 * Listen for changes to the network service state (cellular).
63 * Listen for changes to the network signal strength (cellular).
74 * Listen for changes to the message-waiting indicator.
88 * Listen for changes to the call-forwarding indicator.
99 * Listen for changes to the device's cell location. Note that
115 * Listen for changes to the device call state.
123 * Listen for changes to the data connection state (cellular).
130 * Listen for changes to the direction of data traffic on the data
141 * Listen for changes to the network signal strengths (cellular)
    [all...]
  /external/clang/test/Sema/
conversion.c 45 c = (short) BIG; // expected-warning {{implicit conversion from 'short' to 'char' changes value}}
46 c = (int) BIG; // expected-warning {{implicit conversion from 'int' to 'char' changes value}}
47 c = (long) BIG; // expected-warning {{implicit conversion from 'long' to 'char' changes value}}
50 s = (int) BIG; // expected-warning {{implicit conversion from 'int' to 'short' changes value}}
51 s = (long) BIG; // expected-warning {{implicit conversion from 'long' to 'short' changes value}}
55 i = (long) BIG; // expected-warning {{implicit conversion from 'long' to 'int' changes value}}
78 return (long long) BIG; // expected-warning {{implicit conversion from 'long long' to 'char' changes value}}
81 return (long) BIG; // expected-warning {{implicit conversion from 'long' to 'char' changes value}}
84 return (int) BIG; // expected-warning {{implicit conversion from 'int' to 'char' changes value}}
87 return (short) BIG; // expected-warning {{implicit conversion from 'short' to 'char' changes value}
    [all...]
knr-def-call.c 39 proto(42.1); // expected-warning{{implicit conversion from 'double' to 'int' changes value from 42.1 to 42}}
40 (&proto)(42.1); // expected-warning{{implicit conversion from 'double' to 'int' changes value from 42.1 to 42}}
  /developers/build/prebuilts/gradle/MultiWindowPlayground/kotlinApp/Application/src/main/java/com/android/multiwindowplayground/activities/
CustomConfigurationChangeActivity.kt 23 * This activity handles configuration changes itself. The list of configuration changes that are
  /developers/samples/android/ui/window/MultiWindowPlayground/kotlinApp/Application/src/main/java/com/android/multiwindowplayground/activities/
CustomConfigurationChangeActivity.kt 23 * This activity handles configuration changes itself. The list of configuration changes that are
  /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/lib2to3/fixes/
fix_ws_comma.py 1 """Fixer that changes 'a ,b' into 'a, b'.
3 This also changes '{a :b}' into '{a: b}', but does not touch other
  /device/linaro/bootloader/edk2/OvmfPkg/PlatformDxe/
Platform.uni 36 #string STR_SAVE_EXIT #language en-US "Commit Changes and Exit"
37 #string STR_DISCARD_EXIT #language en-US "Discard Changes and Exit"
  /device/linaro/bootloader/edk2/QuarkSocPkg/QuarkNorthCluster/Include/Protocol/
PchInfo.h 31 // Any backwards compatible changes to this protocol will result in an update in the revision number
32 // Major changes will require publication of a new protocol
  /device/linaro/bootloader/edk2/Vlv2DeviceRefCodePkg/ValleyView2Soc/SouthCluster/Include/Ppi/
PchUsbPolicy.h 51 /// Any backwards compatible changes to this PPI will result in an update in the revision number
52 /// Major changes will require publication of a new PPI
  /device/linaro/bootloader/edk2/Vlv2DeviceRefCodePkg/ValleyView2Soc/SouthCluster/Include/Protocol/
PchInfo.h 41 /// Any backwards compatible changes to this protocol will result in an update in the revision number
42 /// Major changes will require publication of a new protocol
  /external/autotest/client/site_tests/crosvm_Sanity/
control 10 This test will detect changes to the virtualization environment and fail when
24 this environment as well as possible. This test ensures relevant changes are
  /external/chromium-webview/
README 27 Due to WebView API changes in the O-MR1 release, the Java code in the Chromium
29 the O-MR1 specific Java changes to Chromium once the final O-MR1 SDK is released.
  /external/clang/test/Rewriter/
rewrite-foreach-in-block.mm 23 // sanity test for the changes.
28 // sanity test for the changes.
  /external/clang/www/demo/
what is this directory.txt 4 Perhaps it could also be used for getting crash information and details on errors.... I'm not sure if this would require some major changes or not to report this info. Maybe also adding ways that people can use it to test for errors and a way to report such errors would also be good.
7 Anyways, right now, these file a basically just a copy of the LLVM+GCC demo (no changes have been made). The files don't even work right in this location on the server. As such, someone will need to edit the file or rewrite it.

Completed in 1034 milliseconds

<<11121314151617181920>>