I am on Staging 1.3.11_1 but this has been there for a few versions.

JUST in the Program section (not Nodes, Integers, State, etc) about every 3-5 sections the screen has a blue line flash under the program heading.

If you have activated search, it will clear the search. Both visually irritating, but mades search a race for time or unusable.

hope this helps.

Edited September 25Sep 25 by sjenkins

Programs are re-evaluating very frequency. Not an issue but is the cause.

The programs list is scheduled for virtualization which will correct, but not sure on the time frame. All improvements to original grids/lists are deferred until virtualization is complete. This is also needed for mobile implementation so is high on the list.

I'm on windows 11 with edge browser, I don't have the blue line issue or the search issue in 1.3.11

Thanks @Javi for the explanation, understand you need to prioritise development just wanted it on the observed list

To @Techman ’s point, I am on osx with Safari, I’ll try with a couple other browsers and see if there are differences and bring back. Maybe it’s a browser quirk.

7 hours ago, sjenkins said:

I am on osx with Safari, I’ll try with a couple other browsers and see if there are differences and bring back. Maybe it’s a browser quirk.

FWIW, I am on Safari and I do not notice any flashing blue line or a clearing of any search results. I just now upgraded to 1.3.11_1 beta (not yet rebooted), however.

Edited September 26Sep 26 by oberkc

Chrome and Edge both show the issue for me. I did submit a ticket and they are going to remote in at some point to take a look at it.

Here is the UDI response.

Hi Brent,

I have replicated and have a good test case. Approval can be revoked.

It may be some time before we have a fix, this was scheduled to be rebuilt so I may bump on the todo list.

Will update in a few days.

The issue is many program updates every second (see control _1 action 0 in the event viewer, the eventInfo has the program ids), most users would likely not never see this. It may be a good idea to find offending programs causing frequent evaluations, there may be an optimization, or shared optimizations, like setting a variable then checking the variable instead of frequent runs, having a shared condition in a folder with the programs as children

Either way it is replicated with a vicious loop .The test case replicates this with a program looping over running and empty program then and else.