Hello people...
I wonder if someone around here has tried to "talk" to proe using custom hardware. Getting signals from custom USB devices is not *that* hard, but how do you get PROE to, for example, recognize that when you press a button in a custom device it means it needs to run X mapkey?
Case in point: if you wanted to use PROE with two mouses, forcing one of them to work with different drivers to avoid conflicts with the primary pointing device, how do you communicate this second mouse' events to PROE? (Or if you wanted to use the gameport, or... you get the idea)
I noticed, for example, that when you install the applications that come with the Spaceball but don't connect it, when you try to run PROE it complaints about not having any spaceball connected... So proe seems to be looking somewhere... but where???
Hints?
JR
I wonder if someone around here has tried to "talk" to proe using custom hardware. Getting signals from custom USB devices is not *that* hard, but how do you get PROE to, for example, recognize that when you press a button in a custom device it means it needs to run X mapkey?
Case in point: if you wanted to use PROE with two mouses, forcing one of them to work with different drivers to avoid conflicts with the primary pointing device, how do you communicate this second mouse' events to PROE? (Or if you wanted to use the gameport, or... you get the idea)
I noticed, for example, that when you install the applications that come with the Spaceball but don't connect it, when you try to run PROE it complaints about not having any spaceball connected... So proe seems to be looking somewhere... but where???
Hints?
JR