forums.ps2dev.org

umm here this might help.

varlist = {
funct()
do stuff here... etc

end,

funct()

more stuff here

end,

etc..

}

varlist[1]() 2 3 etc.. can be called using this

You can also define functions as variables.

functionX = funct(foo)
do stuff here

end

How about I say no.

maybe just have a faster blitting system.

why wouldn't you? try: (code works) function SubMain() screen:print(0,0,"test",Color.new(255,0,0)) end function Main(func) while true do screen:clear(Color.new(255,255,255)) fun...

Yes Variables are handled as functions. So any variable can be passed off as a function If it doesnt error out that is. function Main(pName, pStuff) if (type(pName) == "function") then result = pName() -- result is whatever pN...

I used it as a refrence.. not as actual code. the reason why it has this problem is because its relational variables. Not direct data based variables. Tables, functions, threads, and (full) userdata values are objects: variables do not actually contain these values, only references to them. Assignme...

tostring(block[1])

use that..

SSphear you are absolutly right '\0' is used by c programmers as a char[] terminator to avoid any errors during output. The length still remains the same. Even the string behind char[] remains the same. While the data is not lost. char[] simply overwrites the data up to a certain level. What that me...

agreed

in c the \0 is to signify the end of the entire string. LUA is useing the same format.

pad = controls.read()

Actually its a quite intuitive answer. sio.cpp:175: error: invalid conversion from 'int (*)(PspIoDrvFileArg*, u32, long long int, int)' to 'SceOff (*)(PspIoDrvFileArg*, SceOff, int)' SIO.CPP is not in the LUAplayer Source files. Which means they have to be the SDK especially if it is useing the SCE ...

When you program. think if i were a computer how would i code myself. It kinda helps.. actually

install the PSPSDK

I dont really have a tutorial. But I do have an example useing a Corutine SDK I made. Process_LIB = { ["ThreadList"] = { }, Exit = nil } function Process_LIB:init () while true do if (self.Exit) the...

Eliminate blitting, and use less code. Less is more!The more functions you use the slower it becomes. The less functions you use.. can also slow it down. Find the right combination. Also use the blit buffer! Only reblit changes in the picture. Never do more than that. Complex code makes it harder fo...

The biggest problem with LUAPlayer is that it uses a single thread for almost everything. When you blit/print too many images during each frame the entire system gets choppy and slows down. In order to decrease the time between. Just remember kids Simpler is better! I do believe you should totally r...

perhaps since LUA checks for commands first

Check if they exist! as variables

if (System.powerGetBatteryLifePercent) then
do it here!

end

that was totally uncalled for be2003. But heres the answer you are waiting for. file_list = System.listDirectory() for key, file in file_list do print("File Name".. file.name.." : ".. file.size) if (file.directory()&...

I actually think 5.1 has increased luaplayers speed substancially, I also have noticed that parsing files (reading) takes absolutly no time to do. Its fantastic! However saving it dead weight.

Actually i tried the other screen as well by using screen.flip() before the copying even starts and it still doesnt copy.

Furthermore here is a workarround for developers to use. (It works just like in dos) IO_LIB = { x = 0, buffer = Image.createEmpty(480, 272), prebuffer = Image.createEmpty(480, 272) } function IO_LIB:PrintF(text) for i = 1, str...

get a serial cable to debug... - or just print to the screen... print() is the function i am talking about for such matters. Instead of, screen:print(0, 0, "text", color.new(0,0,0)) screen.waitVblankStart() screen.flip() For each variable output is perposterous just for the sake of a 30 s...

Printing screen to an image -- Pre Image screen:clear(Color.new(0, 0, 0)) screen:print(0, 264, "I have text here", Color.new(255,255,255)) screen.waitVblankStart() screen.flip() ...

I cant use an old version to debug im useing 5.1 syntax for some file manipulation. And if memory serves me file manipulation has a big problem in the windows client.

Also screen.flip() does not allow me to show an output either. I did a work arround but its a nasty hack I would rather not use.

no just the command print() which used to work for debugging purposes.

neither work

print("string") does not work anymore?! any reasons why?

Im using v0.20 I noticed it does not work in 0.18+

You can also free up memory by deleting the LRX files since they seem to load up into memory at the time LUAPlayer loads up, this can decrease the active memory usage. However some of your demo games may not work. Choose wisely!