Main > Software Forum
.117u1 and What it means to control viewers...
Howard_Casto:
Just some more info...
Compiled a version of u1 just to see what I was in for, control-wise.
The constants are exactly the same, assuming you are mapping stuff to keyboard1:
It's KEYCODE_(Key) , with (Key) being the constant name.... This is good as thankfully, we don't have to re-edit all of our cfg/ctrlr files.
Now even when using -multikeyboard, the first keyboard uses the old standard, which is good. Subsequent keyboards use a number to denote the keyboard, much like joysticks and mice do to give an example of mapping a button to lctrl on the second keyboard:
KEYCODE_2_LCTRL
It's that simple! aside from finding a clever way to add all those constants as options in the viewer, changing the actual parsing code should be quite simple, no major changes so nothing major to change, aside from the fact that when the user is NOT using multikeyboard, the number in the middle has to be ignored... same for multimouse.
Now the interesting thing is that mice are NOT setup this way. When mapping functions to mouse 1, It's always:
MOUSECODE_1_(input)
So keep that in mind.
I'll add more as I discover more... this is much easier for me than tracking notes.
Howard_Casto:
Just a quick note.... there is a bug in .117u1 causing ctrlr files to crash if they don't use a "remap" entry somewhere... you'll get a "malloc zero bytes" error.
Just thought I would mention it.
Getting back on topic... I have no clue how the new joystick_map function works... the only two options seem to be "auto" and "auto_select" so I'll have to look through the source. This would be our most drastic change and therefore needs to be addressed.
headkaze:
Hey Howard do you want me to send what I've written so far for the Input Bible?
Right now I'm just getting the main information into a html file (you got something like FrontPage I hope), so perhaps you can start adding bits and pieces and we can merge them later?
Howard_Casto:
Sure...you can send it on over....
Actually no, I'm old school... use notepad for html. :)
u_rebelscum:
--- Quote from: Howard_Casto on July 22, 2007, 07:42:54 pm ---Getting back on topic... I have no clue how the new joystick_map function works... the only two options seem to be "auto" and "auto_select" so I'll have to look through the source. This would be our most drastic change and therefore needs to be addressed.
--- End quote ---
Check out the new docs/config.txt file. It goes into pretty good depth.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version