V4.0 testing [was V3.7]

[Mint-Gecko]

I’m digging the new look of the buttons. Much easier to differentiate the pressed state from the unpressed state!

My controller seems to be unable to perform a downgrade from v4.0.0a. When loading that firmware selection screen and clicking on any firmware (like v3.6.1), the E1 will freeze and nothing happens (been waiting for over 30 minutes). Can you confirm (and warn people as this can be unexpected) or am I doing something wrong here?

Also, there’s a regression with the painting, esp. groups are broken now when changed via script:

@martin

yes, I did. I can see that some of the visual changes you run there trigger repaints of all components on the screen. And this is happening several (too many) times for each button press. There is a manual away of resolving that by using Lua function to stop and resume the window repaint processing. That would definitely improve things, I am trying, however, as part of the work on the 3.7/4.0 make changes so that the (lua) preset developers do not need to do this manual control of the repaint process.

Did the speedup make it into the new current v4.0? I’m not noticing any changes there.
My script did use the Lua functions to stop and resume the window repaint process. But because there was no noticeable improvement, I disabled this in the lua script. The script stopped the repaint process when changing parameter names, control visibility, parameter range our group name/order. Should that be enough or should the process be stopped for more changes? I noticed some UI stutter when also stopping the repaint process on incoming value changes, so I tried to be a bit conservative with that function.