<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/d794a7965df54225bf5b5bb78ac1dadb&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/d794a7965df54225bf5b5bb78ac1dadb-88da3bdf21bfbd52.gif</thumbnail_url><duration>57.216</duration><title>Ensuring Settings Save on Export</title><description>This Loom explains how the PR ensures settings are saved and applied immediately during the new export. The speaker notes that when the dialog closes, the config tree refresh is called now instead of relying only on onClose. They also describe using flushSettingRights on export so settings are written using the same mechanism as the base referenced ticket. The main goal is to make sure these updates happen before the dialog is closed.</description></oembed>