Note: the performance hit is very apparent when you have huge (2001 outputs, in this case) transactions being computed over every frame (txid, etc?). The fix would be as simple as some kind of intelligent triggerUpdate method that could be called whenever there's an update that potentially involves some ui element
Note: the performance hit is very apparent when you have huge (2001 outputs, in this case) transactions being computed over every frame (txid, etc?). The fix would be as simple as some kind of intelligent triggerUpdate method that could be called whenever there's an update that potentially involves some ui element