Brian H.

I'm a little confused about this. I've heard occasional remarks about how lcd was somehow problematic (either technically or programmatically?). But it also seems incredibly useful & flexible, as evidenced in some of Cycling's own examples. I don't see any explicit suggestions in the docs for alternatives, and anything I've heard mentioned seems considerably more complex (I.e. less accessible). My curiosity would be interested in some background, and my practical side would be interested in some object suggestions that make a case for lcd being truely expendable.

I'm a little confused about this.  I've heard occasional remarks about how lcd was somehow problematic (either technically or programmatically?).  But it also seems incredibly useful & flexible, as evidenced in some of Cycling's own examples.  I don't see any explicit suggestions in the docs for alternatives, and anything I've heard mentioned seems considerably more complex (I.e. less accessible).  My curiosity would be interested in some background, and my practical side would be interested in some object suggestions that make a case for lcd being truely expendable.

lcd-deprecation

I think it's been replaced by jit.mgraphics.

I'm trying to wrap my head around the deprecation of lcd as well. In particular, I'm curious about the sprite functionality of lcd. How do you implement that in jit.mgraphics? Thanks.

sprites is the only thing i dont use because i think it is a bit strange implemented.

and if i need to use layers and copy modes and stuff, i just switch to jit.lcd.

Thanks, Roman. I have some nice functionality using sprites with [lcd], but I can't figure out how to do something similar with [jit.mgraphics]. I see that [jit.lcd] is not deprecated, but I don't see that it has sprite functionality either.

[lcd] deprecation....