xLIB v0.6b Testing

dysfunction · Post by **dysfunction** » Fri 23 Dec, 2005 4:13 am

kalan_vod · Post by **kalan_vod** » Fri 23 Dec, 2005 4:56 am

-16x16 tile mapping works
Just to say whenever you don't need to use the 16x16 tile mapping you don't have to include the tile_size.

Code: Select all

real(2,Matrice_Name,X_Offset,Y_Offset,MapWidth,MapHeight,ScreenStartX,
ScreenEndX,ScreenStartY,ScreenEndY,mPIC_Num,Tile_Method,Map_UpdateLCD

is all you have to include in order to draw 8x8, but if you want 16x16 you need the other argument

real(2,Matrice_Name,X_Offset,Y_Offset,MapWidth,MapHeight,ScreenStartX,
ScreenEndX,ScreenStartY,ScreenEndY,mPIC_Num,Tile_Method,Tile_Size,Map_UpdateLCD

That is also the case with anything thatÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢s added in this update.
-The inverse text works
-All functions from the previous version works
Also the drawshape function works with out the DrawShape_UpdateLCD in

Code: Select all

real(12,Shape_Type,x1,y1,x2,y2,DrawShape_UpdateLCD

use

real(12,Shape_Type,x1,y1,x2,y2

instead

I am still working on testing and so far it's great

!
p.s. Would you like us to report errors in the read me or updates needed to the read me?

dragon__lance · Post by **dragon__lance** » Sat 24 Dec, 2005 1:41 am

um, when u use the 16*16 tilemapper(which rocks), and use the bottom row of sprites on the screen, sometimes it gives little dots at the bottom of the sprite on the screen, don't really kno if this was reported before...
curious thing is, not all of the bottom spriterow gives garbage, only some...

merthsoft · Post by **merthsoft** » Sat 24 Dec, 2005 3:24 pm

Yeah, that was something that had happened even in the early days of xLIB...

Post by **tr1p1ea** » Sat 24 Dec, 2005 5:17 pm

Strange, ill check into it.

kalan_vod · Post by **kalan_vod** » Sat 24 Dec, 2005 6:00 pm

Try reseting your ram, I was trying to copy an archived program and it wouldn't work and then I reseted the ram and enabled xlib and it worked.

DarkerLine · Post by **DarkerLine** » Sat 24 Dec, 2005 10:16 pm

It's 'cause picture variables are only 63 pixels tall, and xLIB tries to read the 64th row of pixels. Just don't use the bottom row.

dysfunction · Post by **dysfunction** » Sun 25 Dec, 2005 1:47 am

Hey tr1p? You gonna send me the beta?

necro · Post by **necro** » Sun 25 Dec, 2005 3:12 am

could you have it just read the bottom row as white?

Spellshaper · Post by **Spellshaper** » Sun 25 Dec, 2005 6:12 pm

IÃƒâ€šÃ‚Â´d like to test the new xLib too...
Send it when u find the time

(It took me long to register here... I had to try 4 times

stupid verification e-mail couldnÃƒâ€šÃ‚Â´t find its way into my mailbox lol)

my e-mail-address is
denix_buri@web.de

DarkerLine · Post by **DarkerLine** » Sun 25 Dec, 2005 7:20 pm

necro wrote:could you have it just read the bottom row as white?

Makes the old and new versions of xLIB incompatible. There is a way to get around the bottom row problem, but it requires some work from you in creating the picture.

dragon__lance · Post by **dragon__lance** » Sun 25 Dec, 2005 7:40 pm

please explain...thatd help alot, such a shame to waste (6) 16*16 tiles

merthsoft · Post by **merthsoft** » Sun 25 Dec, 2005 7:51 pm

Or 12 8x8 ones

Spellshaper · Post by **Spellshaper** » Sun 25 Dec, 2005 7:55 pm

IÃƒâ€šÃ‚Â´ve pondered about this problem, too...
right now IÃƒâ€šÃ‚Â´m just using 16*15 sprites for the last row, then for displaying a 16*16 sprite I check

if itÃƒâ€šÃ‚Â´s the last row, then set the y-width to 15 instead of 16 *shrugs*

necro · Post by **necro** » Sun 25 Dec, 2005 8:15 pm

I meant just read the bottom row of pixels on pictures as white, not the whole sprite