debugPrintBeginFrameBannerdebugPrintEndFrameBannerdebugPrintScheduleFrameStacksdebugTracePostFrameCallbacks debugAssertAllSchedulerVarsUnsetrunAppdebugProfilePaintsEnableddebugPrintLayoutsWidgetsBinding drawFrameSchedulerBindinghandleBeginFramebool scheduleFrameTickerAnimationController RenderObjectmarkNeedsLayoutStatesetState debugPrintScheduleBuildForStacksString FlutterErrorWœ®à­Ý¥—HaG{Ëw0Qpackage:flutter/foundation.dart‹ãšX<€†€¤€¥€Ö (FOPz{Õèé‚‚ ‚m‚¸‚¼ƒƒUƒ¦ƒÔƒØ„!„p„…„‰„—„›„à… …[…r…®…Ú†††1†5†}†Â†é†ê‡&‡*‡‡»ˆ ˆ;ˆ?ˆ‹ˆ³ˆßˆà‰‰‰h‰¸ŠŠŠuŠyŠÆŠòŠö‹f‹‘‹’‹ç‹ëŒ:ŒbŒfŒ·ŒÁŒøHjp‰˜š€ /// @docImport 'package:flutter/rendering.dart'; /// @docImport 'package:flutter/widgets.dart'; /// /// @docImport 'binding.dart'; /// @docImport 'ticker.dart';PŒçŒç Œî‹’‹’‚ŒÆ./// Returns true if none of the scheduler library debug variables have been changed. /// /// This function is used by the test framework to ensure that debug variables /// haven't been inadvertently changed. /// /// See [the scheduler library](scheduler/scheduler-library.html) for a complete /// list.…ü…ßé„…߃ð/// Print a banner at the beginning of each frame. /// /// Frames triggered by the engine and handler by the scheduler binding will /// have a banner giving the frame number and the time stamp of the frame. /// /// Frames triggered eagerly by the widget framework (e.g. when calling /// [runApp]) will have a label saying "warm-up frame" instead of the time stamp /// (the time stamp sent to frame callbacks in that case is the time of the last /// frame, or 0:00 if it is the first frame). /// /// To include a banner at the end of each frame as well, to distinguish /// intra-frame output from inter-frame output, set [debugPrintEndFrameBanner] /// to true as well. /// /// See also: /// /// * [debugProfilePaintsEnabled], which does something similar for /// painting but using the timeline view. /// * [debugPrintLayouts], which does something similar for layout but using /// console output. /// * The discussions at [WidgetsBinding.drawFrame] and at /// [SchedulerBinding.handleBeginFrame].†â†Ç†€ã†Ç€½/// Print a banner at the end of each frame. /// /// Combined with [debugPrintBeginFrameBanner], this can be helpful for /// determining if code is running during a frame or between frames.ˆØˆ¸†êóˆ¸È/// Log the call stacks that cause a frame to be scheduled. /// /// This is called whenever [SchedulerBinding.scheduleFrame] schedules a frame. This /// can happen for various reasons, e.g. when a [Ticker] or /// [AnimationController] is started, or when [RenderObject.markNeedsLayout] is /// called, or when [State.setState] is called. /// /// To get a stack specifically when widgets are scheduled to be built, see /// [debugPrintScheduleBuildForStacks].‹Š‹kˆà‚¯‹k‚…/// Record timeline trace events for post-frame callbacks. /// /// When this flag is set to false (the default), the developer timeline /// records when post-frame callbacks are running, but it does not tell you any /// information about how that time is spent within specific callbacks: /// /// ![](https://flutter.github.io/assets-for-api-docs/assets/scheduler/debug_trace_post_frame_callbacks_off.png) /// /// When this flag is set to true, timeline events will be recorded for each /// post-frame callback that runs, like so: /// /// ![](https://flutter.github.io/assets-for-api-docs/assets/scheduler/debug_trace_post_frame_callbacks_on.png)€®package:flutter/rendering.dart€ßpackage:flutter/widgets.dart binding.dart1 ticker.dartX<€†€¤€¥€Ö (FOPz{Õèé‚‚ ‚m‚¸‚¼ƒƒUƒ¦ƒÔƒØ„!„p„…„‰„—„›„à… …[…r…®…Ú†††1†5†}†Â†é†ê‡&‡*‡‡»ˆ ˆ;ˆ?ˆ‹ˆ³ˆßˆà‰‰‰h‰¸ŠŠŠuŠyŠÆŠòŠö‹f‹‘‹’‹ç‹ëŒ:ŒbŒfŒ·ŒÁŒøHjp‰˜šdebugPrintBeginFrameBannerdebugPrintEndFrameBannerdebugPrintScheduleFrameStacksdebugTracePostFrameCallbacks debugAssertAllSchedulerVarsUnset8Ø