forums.ps2dev.org

[lgnr]

It got a little bigger than i expected. I'll try to explain:
I was writing/learning with a controller homebrew to use with some WinAPI stuff. That turned out to be really fun and useful. Here starts my problem:
I have used SceCtrlData objects and sceCtrlReadBufferPositive() to get key presses.
Everything was going great untill i felt the need to use key releases events. I know i could have just used sceCtrlReadBufferNegative(), but another solution seemed more easy and usefull, since it gets just ONE key press, which is what I'm looking for. So in one of the topics here, someone suggested using SceCtrlLatch and sceCtrlReadLatch(), which is great. Everything worked out. Its all working. Only problem is: PSP freezes on program exit.

Here the main loop from main.c:

[Devun_06]

If you get the home button, your code skips to send the information to the socket on a server, then waits a little while to avoid freezing. If you assume waiting will fix the problem, that means another thread must be running that isn't quite finished yet in some cases. If that's the case, use sceKernelDelayThread() and set it to wait long enough for the other thread to complete(I don't know what code is omitted).

If that's not the case, meaning that wait doesn't actually help any, and didn't before, then you need to, or should install the callbacks for the home key. If you do, I suggest you continue to ignore reading it since it'll be handled by the callback thread.

If you don't want to use that method, you need to create a method for reaching your application's final return statement. Call a break or a return if a certain case is met in your main's while loop. You're using an int for button checking, in C, anything above zero is true, so return -1 or lower for a special case, and manually handle the exit(this cannot be done if you have the callbacks setup).

The problem could be your code that's omitted.

[lgnr]

Thanks for the reply. I'll try to handle the home button particularly. But what puzzles me, and what makes me think that the trouble is not with the rest of the code, is that it does NOT freeze with the sceCtrlReadBufferPositive().
I do not run other threads, so i guess thats not the reason.
Anyway, I was thinking that perhaps the problem is with the function. I mean, the functions runs on every key press, since it returns a value and calls the function again. And it creates a new SceCtrlLatch struct everytime.
I'll try to do something like

[Torch]

Add a sceDisplayWaitVblankStart() inside the loop. The syscon sends control packets at 60Hz anyway.

Use this instead of latch.

[Davee]

Might wanna lookup a bit on structures there. :/

[Raphael]

[lgnr]

So just sceDisplayWaitVblankStart(); wont fix it?
Thanks y'all guys.

[lgnr]

sceDisplayWaitVblankStart(); fixed it.

[Torch]

You should really only be using sceDisplayVblankStart() within your rendering loop when you're making a proper application. Its not required for sceCtrlReadBuffer* functions because they already delay internally to keep up with the sampling rate.

There's no need for a separate loop for reading buttons unless you specifically need high resolution buffered input independent of your game FPS.