{"version":"2.1.274","anchor":"query-engine-events-now-dispatched-through-a-frame-notifier","canonical_anchor":"query-engine-events-now-dispatched-through-a-frame-notifier","heading":"Query engine events now dispatched through a frame notifier instead of applied inline","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/query-engine-events-now-dispatched-through-a-frame-notifier","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Query engine events now dispatched through a frame notifier instead of applied inline\n\nEngine events during a query are now deferred to a frame boundary instead of applied immediately\n\n**Unclear.** What user-visible difference this timing change produces is not stated.\n\n**What**\n\nIn the main query-turn handler, incoming engine events used to be applied straight away. They are now routed through a frame notifier that defers applying them until a frame boundary is reached.\n\n**Why**\n\nDeferring event application this way changes the timing of when state and UI updates take effect during a turn, though the finding doesn't specify the visible effect.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}