# Busy indicator include file for script columns **URL:** \ **Category:** Buttons/Scripts\ **Tags:** script, column, jscript, include\ **Created:** [December 24, 2025, 10:52am UTC](https://resource.dopus.com/t/busy-indicator-include-file-for-script-columns/58139 "2025-12-24T10:52:21Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![errante](https://resource.dopus.com/user_avatar/resource.dopus.com/errante/32/61692_2.png) [@errante](https://resource.dopus.com/u/errante)\ **Post date:** [February 24, 2026, 5:24pm UTC](https://resource.dopus.com/t/busy-indicator-include-file-for-script-columns/58139/3 "2026-02-24T17:24:09Z")
Interesting idea. Thanks for sharing it. As you may have noticed, the count easily becomes inaccurate because you assume that when a column is calculated, it applies to all the items in the current tab, which is not always the case (for example, enter a folder, enable the column (the count should be OK); then expand a subfolder: the count will not be OK, since some of the items will not be calculated again). I don't think there's an easy way to know in advance how many items are actually involved in the calculation, as discussed here: > [@Access to involved items in ScriptColumnData](https://resource.dopus.com/t/access-to-involved-items-in-scriptcolumndata/57758): > > When Opus calculate a script column value (for display, filters, etc.), does it already know if there are other items waiting to calculate the same value? I imagine this is true when the value is calculated for viewing, at least. An idea that would … Or maybe do you have an idea to workaround this? --- _[View the full topic](https://resource.dopus.com/t/busy-indicator-include-file-for-script-columns/58139)._