# Scripting between versions 7.8 to 8.1

**URL:** <https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224>\
**Category:** Ignition\
**Created:** [April 9, 2023, 4:51pm UTC](https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224 "2023-04-09T16:51:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![danblibby](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@danblibby](https://forum.inductiveautomation.com/u/danblibby)\
**Post date:** [April 9, 2023, 4:51pm UTC](https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224/1 "2023-04-09T16:51:42Z")

</div>

Hi everyone,  
Has anyone encountered Ignition software freezing up within the designer due to scripting? I imported some navigation windows from a project in version 7.8 with some buttons that are using the "swap" scripting to another window and also an active alarm count indicator and who is logged in indicator. When I try to open any of these navigation windows in the designer it completely locks up and I am unable to edit. If I have to rebuild the nav windows I will, just wondering if I need to be on the look out for other issues. Thanks

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 9, 2023, 5:15pm UTC](https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224/2 "2023-04-09T17:15:15Z")

</div>

I'd give support a call and provide them with the windows, if possible. This isn't expected and we can probably figure out what's causing it.

---

<div class="post-metadata">

**Author:** ![jpark](https://avatars.discourse-cdn.com/v4/letter/j/a88e57/32.png) [@jpark](https://forum.inductiveautomation.com/u/jpark)\
**Post date:** [April 9, 2023, 5:27pm UTC](https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224/3 "2023-04-09T17:27:23Z")

</div>

Try getting rid of the active alarm count indicator.

---

<div class="post-metadata">

**Author:** ![danblibby](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@danblibby](https://forum.inductiveautomation.com/u/danblibby)\
**Post date:** [April 9, 2023, 5:35pm UTC](https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224/4 "2023-04-09T17:35:25Z")

</div>

@jpark , you were correct. That was the item causing the issues.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [April 10, 2023, 1:49am UTC](https://forum.inductiveautomation.com/t/scripting-between-versions-7-8-to-8-1/72224/5 "2023-04-10T01:49:34Z")

</div>

I'm not sure why the vision templates still come with the navigation bar that calls system.alarm.queryStatus, but this is terribly inefficient and should never be called by the gui in Vision. It will cause the gui to freeze while it requests and waits for the gw to return the results. Unfortunately however, the solution is not exactly simple