It's worth noting (just in case you are using it) that rotation in roScreen is not equivalent to rotation in roImageCanvas. Last time I checked, roScreen could only rotate by 90 degree increments.
P.S. We would *happily* write a compatibility library so you could use roScreen like roImageCanvas if rotation was fixed, as we would be doing it anyway to fix KidPaint. Really, the only thing that's kept KidPaint from being fixed from the buggy implementation that exists using multiple (many!) canvases is that the rotation we need can't be achieved through roScreen. We would actually implement rotation ourselves (albeit slowly) if we could convert both directions between bytearray and roBitmap, but that's missing as well last time I checked. In fact that's what blocked us getting a very low-end (slow) VNC client working (the TCP server that speaks the protocol is written already...).
