forums.ps2dev.org

[Barcode]

I'm trying to run a simple program that is mostly text based. I started off by loading a simple image in the background and checking to see if I could get text up (with the simple Hello World). I got that to work, but then I wanted to add a button function to let the user advance to more text.

I got that to work as well, however, you had to hold the button down to view the text or else it goes back to the old text.

I reworked things around and tried something else by calling a function.

Now I get this error message:

error: script.lua:39: <eof> expected near 'end'

Here's my code:

[Benihana]

Lua doesn't mean what it says half the time - and that's not really Lua's fault. It would be near impossible for it to know what you mean when you make a mistake.

If this is your only code, you have an extra end... therefore my guess is that is what is causing your issues. Since I am not at home I can't check for you. Another easy mistake is misspellings, but I couldn't find any of those. A Lua IDE would likely catch such a mistake, as it would highlight the extra end, or throw off indenting. Also it would be useful to mark line 39 so that regardless of formatting everyone else knows what line is causing the error.

As far as buttons, although many people preach against global variables, I recommend it in this case. You can use a variable set to true or false, like buttonDown == true when the button is down. Sometimes I get lost trying to pass variables back and forth between functions.

[MikeHaggar]

Dunno if this is what you want:

[Barcode]

I tried that, but when you press X, the screen goes blank and says "press start to restart" with nothing to show my error.

I'm wanting to make a game that is pretty much text based.

Typically, i want to show a background image and have some kind of text saying "Hit X to continue". When you press X, it will apply a different background and then new text. Then hit X again to continue. Eventually the controls will become more complex to where you have options as to what you want happen. Typically, I'm working on a simple simdate game.

[mikeyleo]

Should the line return "Option2" be there? Is in the main loop. I think when you execute that line you would exit.

[Arwin]

reading the controller is non-blocking, in Lua too. If I understood it correctly anyway. So that means you read the buttons, and then the program just goes on, no matter what is being read.

I'm not at all versed in Lua yet, but I assume that if you want to wait until X is pressed, you do something like

while not Pad:cross() do
Pad = Controls.read()
end

This should wait for a key to be pressed. Put this in your main loop, and move on to the next screen as soon as you've exited that loop.

[LuMo]