Writing a super simple wacom intuos 3 driver for sprite-building and drawing on my TI-84+.
But when I plug in an HID device, (tablet, mouse or keyboard, doesn't matter) and open USBDRV8X as an app, it starts writing raw hex to the screen. It helps me decipher how my wacom is sending data to the calc. For example, xxx0xxxxxx xxx1xxxxxx etc. tell me the status of the pen. Pen down, up, which button is being pressed on the pen itself.
As I am not wanting anything super complicated, like using the tablet buttons, I just want to be able to pass this to an Axe program for parsing. I don't want to have to learn all the ins and outs of USB, like "pipes" or whatever. Not interested. If USBDRV8X is able to output raw data to the screen, there must be an Axe-compatible hexcode to just store it to Ans as a string or something.
Edit: Fixed the textwalliness of the post, and a spelling error. Also, by "Axe-compatible" I mean:
In the past I've tried using hexcodes inside Axe programs using Asm( like it says I can do in the reference. It doesn't give me any errors or anything, it just doesn't work as expected.
I typed it as an AsmPrgm in a sepeate program, and tested it on its own. It worked, so I used Rcl to recall the hex into the Axe program, so I know it wasn't typed incorrectly or anything. I also typed it with and without C9 to no avail.
So I can only assume Axe just needs hexcodes to be made specifically with Axe in mind.
But when I plug in an HID device, (tablet, mouse or keyboard, doesn't matter) and open USBDRV8X as an app, it starts writing raw hex to the screen. It helps me decipher how my wacom is sending data to the calc. For example, xxx0xxxxxx xxx1xxxxxx etc. tell me the status of the pen. Pen down, up, which button is being pressed on the pen itself.
As I am not wanting anything super complicated, like using the tablet buttons, I just want to be able to pass this to an Axe program for parsing. I don't want to have to learn all the ins and outs of USB, like "pipes" or whatever. Not interested. If USBDRV8X is able to output raw data to the screen, there must be an Axe-compatible hexcode to just store it to Ans as a string or something.
Edit: Fixed the textwalliness of the post, and a spelling error. Also, by "Axe-compatible" I mean:
In the past I've tried using hexcodes inside Axe programs using Asm( like it says I can do in the reference. It doesn't give me any errors or anything, it just doesn't work as expected.
I typed it as an AsmPrgm in a sepeate program, and tested it on its own. It worked, so I used Rcl to recall the hex into the Axe program, so I know it wasn't typed incorrectly or anything. I also typed it with and without C9 to no avail.
So I can only assume Axe just needs hexcodes to be made specifically with Axe in mind.
