52// The handler called to service the timer event of the derived class
53virtualvoid handler() = 0;
54
55 /** Set absolute timestamp of the internal event.
56 * @param timestamp event's 32-bit us timestamp
57 *
58 * @warning
59 * Do not insert more than one timestamp.
60 * The same @a event object is used for every @a insert/insert_absolute call.
61 *
62 * @warning
63 * Ticker's present time is used for reference. The wrapping of the 32-bit
64 * timestamp is handled by assuming that the time specified is always in the
65 * future. For reference @see convert_timestamp. This could cause problems
66 * under load, as if the requested time is missed, the event will be scheduled
67 * one whole 32-bit wrap (over an hour) in the future.
68 *
69 * @warning
70 * Despite previous documentation, this sets an absolute time, based on
71 * a wrapping 32-bit timestamp, not a time relative to now. The replacement
72 * Chrono-based call is `insert_absolute(TickerDataClock::time_point timestamp)`,
73 * not `insert(std::chrono::microseconds rel_time)`. However
74 * `insert(5ms)` can be used instead of `insert_absolute(_ticker_data.now() + 5ms)`.
75 * Due to unclear documentation, it's possible some users may have been
76 * doing `insert(5000)` without adding the current time, and they could be
77 * corrected to `insert(5ms)`.
78 *
79 * @deprecated use `insert_absolute(TickerDataClock::time_point timestamp)`
80 */
81MBED_DEPRECATED_SINCE("mbed-os-6.0.0", "Pass a chrono time_point, not an integer microsecond count. For example use `last_chrono_time + 5ms` rather than `last_us_time + 5000`.")
97 /** Set absolute timestamp of the internal event.
98 * @param timestamp event's us timestamp
99 *
100 * @warning
101 * Do not insert more than one timestamp.
102 * The same @a event object is used for every @a insert/insert_absolute call.
103 *
104 * @deprecated use `insert_absolute(TickerDataClock::time_point timestamp)`
105 */
106MBED_DEPRECATED_SINCE("mbed-os-6.0.0", "Pass a chrono time_point, not an integer microsecond count. For example use `last_chrono_time + 5ms` rather than `last_us_time + 5000`.")
This site uses cookies to store information on your computer.
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
Cookie Policy
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.