Golf Tour 2011 - Not mini golf!

[boot2490]

The repeat should recall it...
But, how do you store a 94x62 image to a pic or something? I only know about 8x8.

[Hayleia]

But, how do you store a 94x62 image to a pic or something? I only know about 8x8.

Two ways for including an image into your prog. Both use the fact that the prog is compiled.
-First, you can convert your image into hex by hand and type it in your source as you would do for a sprite.
-Or, and I'm sure you'll use this one you can store your image in Pic7 (for example) and include at the beginning of your code [Pic7]→GDB8. Then, to display your picture, you just do DispGraph(GDB8).
And if you want greyscale, I think that you could store other images in Pic4 and Pic6 and put them at GDB2 and GDB3, store them to the right buffers and use the right DispGraph command, but I don't do greyscale, so I don't know.

[Yeong]

or you can do:
[Pic1]→GDB1
[Pic2]→GDB2
and do this:
Copy(GDB1,L6,768                //Front Buffer
Copy(GDB2,L3,768                //Back Buffer
DispGraph

[boot2490]

How do you make it non pic dependant? Like having a setup program that updated the pics?

[Yeong]

You could store it into appvar.
Make a program that do that.
prgmPROGRAM
.TEST
[Pic1]→GDB1
GetCalc("appvPIC1",768)→A
Copy(GDB1,A,768

This will create the appvar PIC1 that contains Pic1

[boot2490]

Now how do you draw that appvar to the buffer?

[Yeong]

Copy(A,L₆,768

[flyingfisch]

How are you coming along with this project, boot? Do you have an algorithm for me yet?

[willrandship]

Important note: The pic is only needed at compile time, so your users don't need to hang on to it, just you.

Hmm, I should make a var storing axe app, so you can have infinite strings. Handy for BASIC progs that use strings for data.