Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

Make a New PostPrevious ThreadView All ThreadsNext Thread*Show in Threaded Mode


SubjectWhat information would be most helpful for compatibility? new Reply to this message
Posted byCurious
Posted on08/31/02 01:35 AM



Dear Tekhmaster:

Several posts have emerged requesting compatibility with various models of PDA's. I am still looking into various PDA's (still on the sidelines) and hope that I will be able to use your program in the future. From previous posts, you had mentioned that certain bits of information were needed for button mapping and so on. To facilitate compatibility, what information would you need from PDA users? Secondly, how does a user obtain this information from the PDA? (I saw information given in post for the Toshiba e310 and alas, I would not have been able to find that information on a PDA). Thank you.


SubjectRe: What information would be most helpful for compatibility? Reply to this message
Posted byTekhmaster
Posted on10/24/02 05:20 PM



> Dear Tekhmaster:
>
> Several posts have emerged requesting compatibility with various models of
> PDA's. I am still looking into various PDA's (still on the sidelines) and hope
> that I will be able to use your program in the future. From previous posts, you
> had mentioned that certain bits of information were needed for button mapping
> and so on. To facilitate compatibility, what information would you need from
> PDA users? Secondly, how does a user obtain this information from the PDA? (I
> saw information given in post for the Toshiba e310 and alas, I would not have
> been able to find that information on a PDA). Thank you.
>

Sorry for the delay in response.
There are 2 items needed to code for new models.
1. The vender Identification string
2. The key codes for the device.

It seems that every device released seems to switch the key codes around just to be annoying. Compaq even does this on each new model!
I do have a little app that I wrote that tells you all these things when you run it and press buttons. I will have to post a copy on the site ASAP.
Without this you usually need to use snooper apps or get specs from the vendor.

At some time in the future I would like to add a button mapper option this would remove the need for hard coding these things. I think I know the direction to go to make this happen, i just need to free up some development time.


Cheers,
-Techmaster


Previous ThreadView All ThreadsNext Thread*Show in Threaded Mode