Is there a reason KOS only has one controller callback?

[ThePerfectK]

It's a relatively simple fix to add multiple callbacks for multiple controllers in KOS. I use the controller callback as an easy way to define the reboot macro and change what it does depending on screen (i.e. in-game it reboots to title screen, but at titlescreen, it reboots the entire system). Only problem is that there is only one single callback caller defined in controller.c. in retail dreamcast games, usually all 4 controllers can access the reboot macro. I changed controller.c to include 4 callbacks, which can be assigned to each controller, but the problem is making said code portable and expecting others to modify their KOS source the same way.

Is there a reason why there is only one callback defined that I don't see? If not, would it be possible to suggest my changes be rolled into a future revision?

[Protofall]

I came across this callback function when I started learning about the input. I remember BC saying its only really for rebooting/terminating a program early. I don't think its for going from in-game to title-screen like you do there, I didn't even think that kind of action was possible with the callback.

[BlueCrab]

If you're looking to set up a exit to menu callback for all controllers like commercial games do, just set the addr parameter to 0.

[ThePerfectK]

If you're looking to set up a exit to menu callback for all controllers like commercial games do, just set the addr parameter to 0.

I'd like to be able to set unique chords for each controller, though. Example, I have made some changes to controller.h so that each controller has its own unique callback, for instances e.g. Where one controller is a dreamcast pad and the other is a Sega saturn controller or arcade stick or twin stick. Right now, with my small change, the DC reboot sequence is a+b+x+y+start, while an arcade stick or saturn controller is a+b+c+start. The only way I found I could pull that off is if each controller has its own independent callback chord. Is there an alternative way to accomplish that?

[ThePerfectK]

I came across this callback function when I started learning about the input. I remember BC saying its only really for rebooting/terminating a program early. I don't think its for going from in-game to title-screen like you do there, I didn't even think that kind of action was possible with the callback.

You can make your own controller callback function pointer and pass it to the callback mechanism actually. That's why I like using this method for certain actions, with multiple callbacks for each controller I can easily define behavior for multiple different button chords just by changing the behavior of a single function pointer. So if I want the chord to return to title screen when pressed in game but reboot when pressed at the title screen (like how games like sonic adventure or soul caliber work) it's just a matter of changing one function behavior.

[BlueCrab]

If you're looking to set up a exit to menu callback for all controllers like commercial games do, just set the addr parameter to 0.

I'd like to be able to set unique chords for each controller, though. Example, I have made some changes to controller.h so that each controller has its own unique callback, for instances e.g. Where one controller is a dreamcast pad and the other is a Sega saturn controller or arcade stick or twin stick. Right now, with my small change, the DC reboot sequence is a+b+x+y+start, while an arcade stick or saturn controller is a+b+c+start. The only way I found I could pull that off is if each controller has its own independent callback chord. Is there an alternative way to accomplish that?

Other than just checking for the set of buttons in your normal input handling, no, there's nothing in KOS natively to do it.

As was said earlier in the thread, it's meant to be a very simple/stupid way of generally exiting to the BIOS menu that matches what commercial games do (where it's pretty much always ABXY+Start).