Of course, the main problem using MOVE_MEMORY is that it cannot provide a way to XOR memory contents therefore making it impossible to have sprites with transparency. That could be overcome of course using TSPRT from the TurboPTR but that's a non elegant solution, which brings us back to our original problem of moving whole blocks of memory and prioritising. Movement priority is not exactly a necessity but for multi-plane scrolling for example it would be. (eg a moving backgroung (say sky) and a plane moving in an opposite direction)
I might have to contact the current developers of Turbo_TK to see if we could update it a tad :-) (Still believe that two are the best toolkits on the QL, Turbo TK and DIY - TK-II IMHO is QDOS capabilities left out due to lack of time) Phoebus
