| View previous topic :: View next topic |
| Author |
Message |
BaldieJr_01
Guest
|
 Posted: Sat Nov 20, 2004 12:00 am Post subject: Oops! Only 6 joystick axis/ 1 POV? |
 |
|
| Is there any way to read two more axis and one more POV? I have a total of 8 axis and two POV's. |
|
| Back to top |
|
 |
Chris
Site Admin
Joined: 02 Mar 2004
Posts: 10474
|
| Posted: Sat Nov 20, 2004 2:23 am Post subject: |
|
|
It requires changing the program to use DirectInput, which is an area I've never worked in.
Out of curiosity, how important is it? And also, does anyone else have a need for this? |
|
| Back to top |
|
|
BaldieJr_01
Guest
|
| Posted: Sat Nov 20, 2004 3:35 pm Post subject: |
|
|
| Speaking for myself, i'd rate it a 5 on a 1-10 scale. I'd like to see it, but I can live without it if need be. |
|
| Back to top |
|
|
Chris
Site Admin
Joined: 02 Mar 2004
Posts: 10474
|
| Posted: Sat Nov 20, 2004 11:46 pm Post subject: |
|
|
| Thanks. I'll make sure it's on the to-do list for a later time. |
|
| Back to top |
|
|
J-Star
Joined: 19 Feb 2005
Posts: 7
Location: Sweden
|
| Posted: Sat Feb 19, 2005 8:18 pm Post subject: |
|
|
I too am looking for more than 6 + 1 since I have 3 POV hats on my stick (Logitech Wingman Interceptor).
Getting joystick input from DI is not at all difficult. Check out the Joystick sample in the DirectX SDK.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/directx/input/samps/joysticksample.asp
Most of the work would be to toss out the JOYINFOEX struct and replace it by something that can handle 6 axis, 2 sliders and 4 POV hats. Also the script parser have to be updated which is some tedious work.
I'll poke around in this a bit myself but since I'm only explicitly looking for something that will remap my 2:nd and 3:rd POV hats to keyboard combos it's not very likely I'll patch AutoHotKey for this.
/J |
|
| Back to top |
|
|
Chris
Site Admin
Joined: 02 Mar 2004
Posts: 10474
|
| Posted: Sun Feb 20, 2005 2:06 am Post subject: |
|
|
Thanks for the link. Some of my concern about DirectX is retaining compatibility with older systems such as NT4/95 that might lack a recent version of DirectX. In other words, should the DirectX function calls be dynamically loaded via GetProcAddress(), etc.
Also, perhaps the old joyGetPosEx() method should be retained somehow -- in addition to the new DirectX method -- to avoid breaking existing scripts that run on systems with an old DirectX. |
|
| Back to top |
|
|
J-Star
Joined: 19 Feb 2005
Posts: 7
Location: Sweden
|
| Posted: Sun Feb 20, 2005 9:30 am Post subject: |
|
|
| Chris wrote: | Thanks for the link. Some of my concern about DirectX is retaining compatibility with older systems such as NT4/95 that might lack a recent version of DirectX. In other words, should the DirectX function calls be dynamically loaded via GetProcAddress(), etc.
Also, perhaps the old joyGetPosEx() method should be retained somehow -- in addition to the new DirectX method -- to avoid breaking existing scripts that run on systems with an old DirectX. |
Backwards compatibility is always a PITB, however experience shows that there will always be at least one...
Other possible solutions would be to modularize the code so that you for instance can pick diffent DLL's to load depending on which OS the user is running. Today you're a bit too highly integrated and dependant on the types (such as JOYINFOEX).
Or to simply give up on the backwards compatibility for NT/Win 95 but keep the old versions available for those that want that. 
/J |
|
| Back to top |
|
|
BoBo
Guest
|
| Posted: Sun Feb 20, 2005 9:38 am Post subject: |
|
|
Let's wait and see what happens when Microsaft starts with its strict (security/patch) update policy. Some parts of the world will have to swap back to Win1.0 to have a legal package available 
Time to check out Linux (if haven't done already!) |
|
| Back to top |
|
|
J-Star
Joined: 19 Feb 2005
Posts: 7
Location: Sweden
|
| Posted: Sun Feb 20, 2005 9:44 am Post subject: |
|
|
| BoBo wrote: | Let's wait and see what happens when Microsaft starts with its strict (security/patch) update policy. Some parts of the world will have to swap back to Win1.0 to have a legal package available
Time to check out Linux (if haven't done already!) |
We'll see. I don't think Microsoft are foolish enough to enforce a strict policy because then they would go down in no-time. The reason for their success is proliferation. Put an dent in the proliferation and they will lose.
Also, concidering how they are just now publishing lighter variants of the development tools for free (something which the competitors have done for a long time now) I think we're seeing a trend breaker here.
I doubt they will go through with it. If they still do though, there is a chance we'll see another "New Coke" scenario.
/J |
|
| Back to top |
|
|
jonny
Joined: 13 Nov 2004
Posts: 3004
Location: Minnesota
|
| Posted: Sun Feb 20, 2005 4:05 pm Post subject: |
|
|
| Quote: | | Time to check out Linux (if haven't done already!) |
It's always this time.  There are way too many people out there who don't even know Linux exists, let alone that are willing to try it, even though there's distros like Xandros and Linspire that are designed to be easy-to-use and similar to Windows. This is mainly because the incredibly stupid Linux community has fashioned an image for Linux of being "hacky," console-based (you seriously don't have to touch a console if you don't want to in some distros), and only made for that skinny teen in the basement playing MUDs and hacking his friends' IM clients. Marketing plays a big role in any business field, but here it is the crucial factor, and just as many Linux aficionados realize this as there are people who don't have a clue. Linux cannot keep its image if it is to become mainstream.
Of course, one thing that would help is Microsoft finally losing in court and being broken up like it should've been all along. Then perhaps we could have a fair, legal market. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
