# GrapeCity.ActiveReports.Design.Designer.ScriptChanged

## Content

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




<h1 id="GrapeCity_ActiveReports_Design_Designer_ScriptChanged" data-uid="GrapeCity.ActiveReports.Design.Designer.ScriptChanged" class="text-break">ScriptChanged Event
</h1>
<div class="markdown level0 summary"><p>Occurs after modifications have been made to the report's script.</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_ScriptChanged_syntax">Syntax</h5>
<div class="codewrapper">
  <pre><code class="lang-csharp hljs">public event ScriptChangedEventHandler ScriptChanged</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.ScriptChangedEventHandler.html">ScriptChangedEventHandler</a></td>
      <td>Occurs after modifications have been made to the report's script.</td>
    </tr>
  </tbody>
</table>
<h5 id="GrapeCity_ActiveReports_Design_Designer_ScriptChanged_remarks"><strong>Remarks</strong></h5>
<div class="markdown level0 remarks"><p>This event signals that changes have occurred to the script associated with the report. It is particularly useful for scenarios where the script is being
edited directly within the designer or through an external editor integrated into the design environment. Handlers for this event can be used to compile
the script, check for errors, or update UI elements to indicate the script's modified status.</p>
</div>
</div>