Sprite(1000) compared to sprite (10,10)

[Atom Ant]

Sprite(1000) means you can have 1000 pixels max in that sprite. Sprite(100) means you can have 100 pixels max in that sprite.

Basically, Sprite(n) means you can have n pixels max in that sprite.

[Pyrokid]

yes i know but does it really matter

[Anonymous]

if youre in screen 13, using INTEGER arrays to store data, the formula is

((x * y) \ 2) + 2 number of indices to hold a sprite of dimensions x,y.

btw sprite(1000) actually has 1001 indices

anywho

you could fit a 50*40 sprite in sprite%(1001) (2000 pixels in 1002 indices)

((50 * 40) \ 2) + 2 = 1002


sorry, just didnt want you guys to learn wrong


edit: and the difference is, the more indices you use, the more mempry your prog will use. if youre using integer arrays (which i HIGHLY recommend) you will use 2 bytes per index. so the above example with sprite%(1001) will use 2004 bytes.

[Nemesis]

Personally, I like to use multi-dimensional arrays for sprites. If you're a beginning QBasic programmer though, you'll probably want to use a single dimensional array because of simplicity.

Umm, a multi-dimensioned array I feel would be easier for a beginner, than a single dimensioned one.
(That's ofcourse if all the frames of the sprite are the same size.

Nemesis

[na_th_an]

It's the same, but the 2D array approach isn't forwards compatible with FB as it uses row order as opposed to QB which uses column order, so you have to change the order of your dimmensions to make the source compilable in FB.

AARGH!!! Where did you get the info?? Now I understand some things...

I noticed it when I was first testing lillo's GFXlib by porting some old code. I told him that he should include this detail in the docs. I guess he hasn't... or maybe you didn't RTFM :lol:

[Antoni Gual]

Lillo did his homework.. it is in TFM, in the PUT section.

[Pyrokid]

ok so what should you use if your doing a background