# GrapeCity.ActiveReports.Design.Designer.EditModeExit

## Content

<div class="doc-site-dotnet-api-container">




<h1 id="GrapeCity_ActiveReports_Design_Designer_EditModeExit" data-uid="GrapeCity.ActiveReports.Design.Designer.EditModeExit" class="text-break">EditModeExit Event
</h1>
<div class="markdown level0 summary"><p>Occurs immediately after the designer exits edit mode for a report component.</p>
</div>
<div class="markdown level0 conceptual"></div>
<h6><strong>Namespace</strong>: <a class="xref" href="GrapeCity.ActiveReports.Design.html">GrapeCity.ActiveReports.Design</a></h6>
<h6><strong>Assembly</strong>: MESCIUS.ActiveReports.Design.Win.dll</h6>
<h5 id="GrapeCity_ActiveReports_Design_Designer_EditModeExit_syntax">Syntax</h5>
<div class="codewrapper">
  <pre><code class="lang-csharp hljs">public event EditModeExitEventHandler EditModeExit</code></pre>
</div>
<h5 class="returns">Returns</h5>
<table class="table table-bordered table-condensed">
  <thead>
    <tr>
      <th>Type</th>
      <th>Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><a class="xref" href="GrapeCity.ActiveReports.Design.EditModeExitEventHandler.html">EditModeExitEventHandler</a></td>
      <td>Occurs immediately after the designer exits edit mode for a report component.</td>
    </tr>
  </tbody>
</table>
<h5 id="GrapeCity_ActiveReports_Design_Designer_EditModeExit_remarks"><strong>Remarks</strong></h5>
<div class="markdown level0 remarks"><p>This event is triggered when the designer transitions out of edit mode, which could be due to the user completing their modifications or cancelling
the edit operation. It provides an opportunity to execute custom logic after editing has concluded, such as validation, cleanup, or updating other parts
of the UI in response to the changes made.</p>
<p>Listeners can use this event to perform actions that need to occur once editing is no longer active, ensuring that any necessary adjustments or 
checks are made following the edit session.</p>
</div>
</div>