06-07-2016 02:47 AM
Not yet, but I will do that. Just thought there may be an obscure known case where this kind of thing may occur.
06-07-2016 02:52 AM
Have you tried to use the defer panel upates property?
Maybe it helps.
http://zone.ni.com/reference/en-XX/help/371361H-01/lvprop/pnl_defer_pnl_updts/
trying to put it to true before managing buttons and then restoring it to false could help to solve
06-07-2016 03:22 AM
I had similar problem with Charts. My subvi had one or more charts on the frontpanel. The subvi is loaded into a subpanel.
If the main VI (with the Subpanel) runs constantly (start once, let it run) the cpu usage is ok, but if the main vi itself is called from somewhere, the subpanel always gets a redraw message and the chart will also be redrawn.
Is ok: Frontpanel.vi via Subpanel runs Sub.vi
Is slow: LoopCaller.vi calls Frontpanel.vi vis Subpanel runs Sub.vi
Do you have something like the second?
06-07-2016 07:39 AM
Never got around to DETT, problem solved.
Turns out the Sub-Panel was just a red herring. In the test with subpanel, we had 24 modules running in parallel. Specific changes cause a global trigger and the nmodules were not filtering properly so there were 24 modules all doing unneccessary stuff whenever one channel did something. Fixed the filtering and the problem pretty much went away.
Of course testing without subpanel was done with only a handful of modules running and the effect was small enough to be negligible.