EDIT: Link was fixed

The BOXSHIFT command is nowhere near "fully" implemented. That command still needs to be tested and once I can get the logic down correctly, I'll be finishing up with the rest of the code to bring it to fully implemented status.

Though, I would like to hear about how it *could* be implemented. You know, something to provide a little motivation to bring it to completion.

well he has to do some shifting, so he could use this instead or something like that, I hadn't really thought it out, but yeah...I was sure he could think of something

As far as shifting goes, I think what could be done to simulate "smoothscrolling" of sorts would be to have a black border the same width as a "tile" to cut off the work area for the screen when it's updated. The work area, juggled around in a pic file, would contain the stuff used by the boxshift routine to perform said shift. Then again, xLIB has a command a little like that which would be a bit more economical (fullscreen shifts). At least, I *think* it has a command for it. If not, then it certainly is a part of Celtic III as I remember the pains of coding in such a routine.

xLib does have fullscreen shifting, and I can't seem boxshift to do anything except give strange errors.  Maybe because it is in production and not finished?

EDIT: Link was fixed

The BOXSHIFT command is nowhere near "fully" implemented. That command still needs to be tested and once I can get the logic down correctly, I'll be finishing up with the rest of the code to bring it to fully implemented status.

Though, I would like to hear about how it *could* be implemented. You know, something to provide a little motivation to bring it to completion.

QFT

well right now I have very good speed using xLibs shiftscreen method, so I doubt i will ever need it And i forgot to mention, that this program only displays the status every other shift, so you can actually get twice the framerate if you mix around the code a bit.  (but not twice the speed)

Scrolling left/right, however, is going to be very difficult, because I would have to display 40 sprites for every 1/2 sprite shift and this takes about 1 second on my SE.  So it would probably be more practical to just redraw the entire screen under the cover of no buffer update, and shift the screen, like, 2 or 3 spaces.  A total screen redraw takes 1.5 seconds on my SE, which isn't that bad if the screen can be shifted an arbitrary amount right or left. 

Blarg.

So i was working on how to get an object to display correctly, and if you want the object to be masked, these are the steps

save screen
clear screen
draw object
mask object with above 3 land masks
save pic
clear screen
draw object mask
mask mask with above 3 land masks
save pic
recall landscape
AND mask pic
OR object pic

thats huge, and all necessary to display a single object.