Make column renderer more efficient

[taauntik]

Forum Post

Hi Bryntum Team,

I just noticed a behavior in the Scheduler that was surprising to me.
The scenario is that I add a custom renderer to a column (below is the code that you can add to the basic scheduler demo, I just added a console log when the renderer is being triggered). Now, there are two things:

1. On every small resize of an event (e.g., just by 1px) a rerender of the complete row (in which the event is being resized) is triggered (1 log per resize)
2. If I drop an event, all (!) rows are being rerendered (10 logs per event drop)

I am wondering, why is it necessary to rerender the columns in both cases anyways, since from my understanding only the event representation changes. For instance, if I have some more or less "heavy" computation inside the renderer this could really affect performance.

Thanks for your help!

[isglass]

PR better optimizes resizing when using lockLayout. When not using it, it currently has to pass through the normal rendering pipe in case the resize leads to a row height change.