Variable window makes BTT's CPU usage to spike

Bugs or Unexpected Behavior
1

Once I open the variable window BTT's CPU usage hits 100% and respectively BTT almost stops responding. I'm wondering if this has something to do with the accelerometer variables, because before it stops responding the "-" sign in front of the these values is constantly appearing/disappearing and additionally as mentioned here once the live view of the accelerometer is open the same happens.

BTT: 6.335 and 6.334

2

Ah yes most likely, I added these variables for testing but they should not be set on every reading in production. Will be removed in the next build.