https://wikiti.brandonw.net/index.php?action=history&feed=atom&title=83Plus%3ASoftware%3Ausb8x%2FAsm_Interface%2FPad%2FPadSetup 2026-04-06T02:57:39Z Revision history for this page on the wiki MediaWiki 1.23.5 https://wikiti.brandonw.net/index.php?title=83Plus:Software:usb8x/Asm_Interface/Pad/PadSetup&diff=5274&oldid=prev 2006-09-10T01:50:44Z

<p></p> <p><b>New page</b></p><div>== Synopsis ==<br /> '''Name:''' PadSetup<br /> <br /> '''Minimum usb8x version:''' 0.11<br /> <br /> Gets an offset and bitmask to help map buttons to functions.<br /> <br /> === Inputs ===<br /> ''None''<br /> <br /> === Outputs ===<br /> * B: Offset byte<br /> * C: Bit mask<br /> * NC: Success<br /> <br /> === Destroys ===<br /> * AF, BC, DE, HL<br /> <br /> == Notes ==<br /> Be sure to initialize the gamepad driver with [[../PadInit|PadInit]] before using this routine.<br /> <br /> PadSetup waits for the user to press a button on the gamepad, and then returns the byte offset into the data array and the bit mask to use to check for that button. You can use this information to determine, from the data passed to the callback function, whether a particular button is being pressed.<br /> <br /> PadSetup will return failure if any one of the following conditions occurs:<br /> # PadSetup cannot determine the offset and bitmask for the button pressed. This means the gamepad is either incompatible or that particular button is not reported in a way that the gamepad driver understands. Analog sticks, for example, will probably not be correctly read by the gamepad driver.<br /> # The function times out (timeout occurs after about 2 seconds). On failure, you can call the function a couple of times to reach the timeout length you would like.<br /> # The user has pressed the [on] button.<br /> <br /> == See Also ==<br /> * [[../PadStart|PadStart]] - Start relaying gamepad data to the callback function.</div>

Dan Englender