06-07-2016 04:54 AM
Hai Gusy! (kudos to the one spotting the referrence)
So, i have a program which has a Main panel with some picture buttons but the rest of the functions go through a tab control. Thus these buttons and the tab control changes visibility every so often.
What happened is that it took 0,5-1sec to change this visibility! I assumed it was the the several visibility properties of the picture buttons causing it, so i moved them to a cluster and thus only needed 1 property node for these buttons, for 2 free property nodes in total, to no avail.
On a hunch i wired the error wire to force seqential order and BAM, <50ms!
So, somehow parallellized visibility change get stuck in some sort of update loop, maybe it forces a redraw for each included control/indicator in the tab control?
The tab control isn't overly crowded, some 50-100 control/indicators over 5 tabs.
LV2011, i'll try it in 2014 on thursday when i'm back at that project.
TL;DR
Parallellized visibility change is borked.
/Y
(Kat durids is 4 fite)
06-07-2016 05:35 AM
I think this is rather an expected behavior. As all these property nodes run in the UI Thread, you have a race condition on the UI thread. I assume that a defer panel updates would also relief the "delay"....
Norbert
06-07-2016 07:28 AM
20-50x time difference isn't expected in my book. 🙂
The sketch in your signature is SOOO good! 😄
/Y