How does BasicBuilder handle the pics? Does it put them in the app or do you have to leave them as normal pics?
BasicBuilder packages the pics into the app just like it does with the programs. However, having the pics as random data in the app is useless if you plan on using Celtic or xLIB with the pics. In order to use the pics, you have to "extract" them from the app first. Basically you have to recall the pics from the app and store the image to pic files.
Bowling stores the images to "hacked" variables and archives them when it is first run. That's what is going on in the background when you see the images flash on the screen.
Just a question about BasicBuilder: can you put multiple programs into it? Because I read somewhere that it didn't work... (I might use that for my Fangh RPG).
By the way, how does xLIB work with BasicBuilder apps?
Yes you can put multiple programs into it, but I find that the application runs extremely slow when there is more than one program packaged into it. To avoid this issue, I compile all the subprograms into the main program. There is a method to call the subprograms from the main code without destroying the flow of execution. If you induce a memory leak using a Goto inside a Repeat/While loop, you can return back into the loop by passing an extraneous End to the interpreter. The interpreter will see the End as part of the exited loop and will resume execution after the loop. In effect, the subprogram code can be called just like it would be if it were a separate program. There a few varieties of methods to induce the memory leak. The method I use allows arguments to pass in Ans which I find useful at times.