Is there any place in the firmware that can be used to demonstrate that it is broken? Without a test runnable in-situ in main it is hard to evaluate if anything is broken or not.
It's the default transition that's used anytime there's no other transition specified and that can be seen in a lot of places in main; gr33nhouse for example.
(or could be seen if it was working ;p it works in 1.2.0)
Pushed a commit that reverts behavior to the behavior of 1.2.0. Any code path that involves full-screen compositing, like clipping and compositing groups are probably going to be slower than desirable until the st3m_ctx ctx-backend also makes use of or implements tiled/chunked rasterization - this is among my goals for 1.4 or 2.0 now that rasterization is happening on stable framebuffers.