Measuring a module's impact on just the UI thread?

Squinky · June 21, 2024, 10:18pm

I was thinking “maybe that why I’ve had problems with drawLayer “!

baconpaul · June 22, 2024, 2:44am

The trick is make a widget containing a frame buffer widgets for your layer then call that widgets draw in you your draw layer.

github.com

surge-synthesizer/sst-rackhelpers/blob/75c7b4efb5371d343f0f56fcfaec54cbd9ea3247/include/sst/rackhelpers/ui.h#L46


      
              BufferedDrawFunctionWidget(rack::Vec pos, rack::Vec sz, drawfn_t draw_) : drawf(draw_)
              {
                  box.pos = pos;
                  box.size = sz;
                  auto kidBox = rack::Rect(rack::Vec(0, 0), box.size);
                  kid = new InternalBDW(kidBox, drawf);
                  addChild(kid);
              }
          };
          
          struct BufferedDrawFunctionWidgetOnLayer : BufferedDrawFunctionWidget
          {
              int layer{1};
              BufferedDrawFunctionWidgetOnLayer(rack::Vec pos, rack::Vec sz, drawfn_t draw_, int ly = 1)
                  : BufferedDrawFunctionWidget(pos, sz, draw_), layer(ly)
              {
              }
          
              void draw(const DrawArgs &args) override { return; }
              void drawLayer(const DrawArgs &args, int dl) override
              {

Squinky · June 22, 2024, 3:57pm

Is it still buffered if you do that?

baconpaul · June 22, 2024, 6:30pm

Yes