Hi all, I was wondering if anyone has tried moving screen memory around using a lookup table instead of calculating the memory position of each pixel every time...
Anyone that has used both methods knows which one is faster? I want to setup up a look-up table containing the memory position of each pixel that will be generated upon a mode change (or whenever I feel like it anyway ;-) That table would be an X (the x coordinate) by Y (the y coordinate) and in each x by y position, the screen memory address that this corresponds to would be contained (and maybe the alternate memory location for swapping)... In that aspect when giving a hypothetical command Draw_Sprite, x,y, instead of calculating every single time what memory address x and y correspond to, the command could look it up a table directly. Surely this wastes memory but I have the feeling that this could SUBSTANTIALLY accelerate "bitblt" operations and in essence be the base of a "software blitter". Of course this cannot apply to the whole memory :-) (It's simply impossible unless a file is used) So any comments? Phoebus P.S. Wolfgang is that what your Setup_Scr is doing? (so I won't have to do it twice)
