Searched full:notifications (Results 1 – 25 of 540) sorted by relevance
12345678910>>...22
| /third_party/flutter/flutter/packages/flutter/lib/src/foundation/ |
| D | change_notifier.dart | 32 /// a mutable value that triggers the notifications when modified.
34 /// The terms "notify clients", "send notifications", "trigger notifications",
35 /// and "fire notifications" are used interchangeably.
40 /// whenever a given [Listenable] triggers its notifications. This widget is
45 /// rebuild whenever a [ValueListenable] object triggers its notifications,
48 /// [Listenable]'s notifications to trigger rebuilds in descendant widgets
51 /// notifications whenever any of a list of other [Listenable]s trigger their
52 /// notifications.
90 /// API using [VoidCallback] for notifications.
94 /// notifications (where N is the number of listeners).
[all …]
|
| /third_party/flutter/flutter/packages/flutter/lib/src/widgets/ |
| D | inherited_notifier.dart | 15 /// Dependents are notified whenever the [notifier] sends notifications, or
18 /// Multiple notifications are coalesced, so that dependents only rebuild once
43 /// sends notifications.
55 /// Whenever this object sends change notifications, the dependents of this
60 /// determined by the `==` operator), notifications are sent. This behavior
63 /// While the [notifier] is null, no notifications are sent, since the null
64 /// object cannot itself send notifications.
|
| D | notification_listener.dart | 20 /// To listen for notifications in a subtree, use a [NotificationListener].
87 /// Notifications will trigger the [onNotification] callback only if their
90 /// To dispatch notifications, use the [Notification.dispatch] method.
92 /// Creates a widget that listens for notifications.
115 /// Notifications vary in terms of when they are dispatched. There are two
118 /// For notifications that dispatch during layout, such as those that inherit
121 /// descendant, by definition, since notifications bubble up the tree). For
143 /// To listen for notifications in a subtree, use a
158 /// ancestors when appropriate, or alternatively, dispatch the notifications
|
| D | scroll_notification.dart | 19 /// Typically listeners only respond to notifications with a [depth] of zero.
44 /// The notifications have the following lifecycle:
62 /// Notifications bubble up through the tree, which means a given
63 /// [NotificationListener] will receive notifications for all descendant
64 /// [Scrollable] widgets. To focus on notifications from the nearest
73 /// notifications are therefore primarily useful for paint effects (since paint
75 /// widgets are examples of paint effects that use scroll notifications.
282 /// listen to notifications from their children.
|
| D | size_changed_layout_notifier.dart | 25 /// notifications such as this one.
50 /// * [Notification], the base class for notifications that bubble through the
54 /// notifications when [child] changes layout size.
|
| /third_party/gstreamer/gstreamer/libs/gst/check/ |
| D | gsttestclock.c | 59 * #GstClock allows for setting up single shot or periodic clock notifications
60 * as well as waiting for these notifications synchronously (using
65 * #GstTestClock keeps track of these clock notifications. By calling
68 * next one or several clock notifications to be requested. Additionally unit
71 * inaccuracy (jitter) of clock notifications, since the test can decide to
77 * notifications so far.
79 * N.B.: When a unit test waits for a certain amount of clock notifications to
82 * for a long time. If they block forever then the expected clock notifications
96 * ## Demonstration of how to work with clock notifications and #GstTestClock
775 * @test_clock: a #GstTestClock for which to count notifications
[all …]
|
| /third_party/node/test/parallel/ |
| D | test-inspector-connect-main-thread.js | 157 const notifications = [];
158 session.on('NodeWorker.attachedToWorker', (n) => notifications.push(n));
160 // 2 notifications mean there are 2 workers so we are connected to a main
162 assert.strictEqual(notifications.length, 2);
|
| /third_party/selinux/libselinux/src/ |
| D | selinux_netlink.h | 2 * Netlink event notifications for SELinux.
19 #define SELNL_GRP_AVC 0x00000001 /* AVC notifications */
|
| /third_party/flutter/flutter/packages/flutter/lib/src/material/ |
| D | scrollbar.dart | 34 /// The [child] should be a source of [ScrollNotification] notifications,
44 /// subtree) should include a source of [ScrollNotification] notifications.
118 // scroll notifications here.
|
| /third_party/node/deps/npm/man/man1/ |
| D | npm-hook.1 | 73 …s \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR,
94 …st \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR
|
| /third_party/selinux/libselinux/man/man3/ |
| D | avc_netlink_loop.3 | 40 opens a netlink socket to receive SELinux notifications. The socket
65 automatic processing of notifications.
|
| /third_party/cef/tests/ceftests/ |
| D | request_handler_unittest.cc | 485 // Verify network notifications for multiple browsers existing simultaniously.
491 // Verify network notifications for multiple browsers existing simultaniously.
498 // Verify network notifications for multiple browsers existing simultaniously.
505 // Verify network notifications for multiple browsers existing simultaniously.
511 // Verify network notifications for multiple browsers existing simultaniously.
518 // Verify network notifications for multiple browsers existing simultaniously.
|
| /third_party/libcoap/include/coap3/ |
| D | resource.h | 55 * Notifications will be sent non-confirmable by default. RFC 7641 Section 4.5
62 * Notifications will be sent confirmable. RFC 7641 Section 4.5
68 * Notifications will always be sent non-confirmable. This is in
96 * If this flag is set, coap-observe notifications
100 * If this flag is set, coap-observe notifications
|
| D | coap_subscribe_internal.h | 30 * Number of notifications that may be sent non-confirmable before a confirmable
39 * Number of confirmable notifications that may fail (i.e. time out without
|
| /third_party/node/deps/npm/docs/content/cli-commands/ |
| D | npm-hook.md | 59 …e [npm hooks](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm),
80 …ks" blog post](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm)
|
| /third_party/flutter/skia/third_party/externals/angle2/doc/ |
| D | ExtensionSupport.md | 31 * reset notifications and sized queries only, no robust buffer access
53 * only reset notifications supported
|
| /third_party/mesa3d/src/virtio/vulkan/ |
| D | vn_ring.h | 14 * mechanism is required for ring setup and notifications in both directions.
15 * Notifications for new data from the producer are needed only when the
|
| /third_party/node/ |
| D | onboarding.md | 53 * Notifications:
54 * Use [https://github.com/notifications](https://github.com/notifications) or
57 notifications on typical weekdays), so be prepared
102 for notifications
|
| /third_party/flutter/flutter/packages/flutter/test/foundation/ |
| D | change_notifier_test.dart | 305 int notifications = 0;
307 notifications += 1;
310 expect(notifications, 0);
313 expect(notifications, 1);
|
| /third_party/libwebsockets/include/libwebsockets/ |
| D | lws-state.h | 55 * lws_state_reg_notifier() - add dep handler for state notifications
80 * lws_state_reg_notifier_list() - add dep handlers for state notifications
|
| /third_party/cef/libcef/browser/ |
| D | browser_platform_delegate.h | 135 // called a single time per instance. Do not send any client notifications
147 // Send any notifications related to browser creation. Called after
151 // Send any notifications related to browser destruction. Called before
158 // called. Do not send any client notifications from this method.
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/include/llvm/ExecutionEngine/Orc/ |
| D | RTDyldObjectLinkingLayer.h | 40 /// Functor for receiving object-loaded notifications.
45 /// Functor for receiving finalization notifications.
195 /// Functor for receiving object-loaded notifications.
200 /// Functor for receiving finalization notifications.
205 /// Functor for receiving deallocation notifications.
|
| /third_party/cef/libcef/browser/prefs/ |
| D | pref_store.h | 18 // contents of the store, triggering notifications where appropriate.
61 // Used for tests to trigger notifications explicitly.
|
| /third_party/libinput/doc/user/ |
| D | switches.rst | 33 This handling of lid switches is transparent to the user, no notifications
61 notifications are sent and the device appears as enabled at all times.
|
| /third_party/libcoap/ |
| D | coap_config.h.contiki | 104 * Number of notifications that may be sent non-confirmable before a
113 * Number of confirmable notifications that may fail (i.e. time out
|
12345678910>>...22