Main > Main Forum
Extra features on the MK64 (wishlist)
Lilwolf:
Thats easy to add... if you run a program.
have 4 buttons that are different on each control panel. then have a program that will start a different CP based on that.
currently it could do 2 with switching between banks. But it would be great if there was a sync program that you could run quickly before each mame call. That would check to see what was last loaded and what leads are currently being pressed... Then load it only if its changed.
btw, I added support to this in my frontend... but I wasn't able to run the keymap from inside java in win98... I should try again now that I'm running XP.
I have another request. Could we have the application keymap changed to a win32 application? I believe this was why I couldn't call it from java.
Also, whats the chance of having the API to change/add/read the application opensourced? I would write a little nice java application that would make configuring it. Open API would be GREAT!
Ron_Michallick:
>I have another request. Could we have the application keymap changed
> to a win32 application? I believe this was why I couldn't call it from java.
>Also, whats the chance of having the API to change/add/read the application
>opensourced? I would write a little nice java application that would make
>configuring it. Open API would be GREAT!
After I finish the firmware changes, I'll revamp the computer side software which has been and will be open source. I wish I knew what open API was. It would also be nice if I could program the board through the window keyboard driver instead of bypassing it.
The Macro function is implemented. Support for dual 12 position rotary switches is half complete. I think thats the last task on my list.
Only 300 Rom words left,
Ron.
Lilwolf:
WHAT??? 12 rotateries???
I LOVE YOU!!! (I have 2 and haven't had the cash for the druin's boards yet! I kept thinking I might find another solution!!!)
SWEET!!
API is a application programming interface. So it would be that your write a dll with function calls that look like this.
setKeys(byte location, char[] keys)
char[] getKeys(byte location)
setBank(boolen bank)
ect. But then you package them without an application. So I can write a program, load the dll, and call setKeys, getKeys ect. without having to figure out the timing and quarks.