gregorypierce
|
 |
«
Posted
2003-08-27 16:21:13 » |
|
Been delayed by two things of late: 1) An unfortunate .Net project 2) Seemingly endless 10.3 release seeds  When 10.3 settles down a bit I'll post another cleaned up release. |
http://www.gregorypierce.comShe builds, she builds oh man When she links, she links I go crazy Cause she looks like good code but she's really a hack I think I'll run upstairs and grab a snack!
|
|
|
|
Jeff
|
|
«
Reply #1 - Posted
2003-09-02 18:43:29 » |
|
Cool, thanks Greg.
Have we decided yet on a standard for how to represent the mouse? (One device or two?)
JK
|
|
|
|
|
gregorypierce
|
|
«
Reply #2 - Posted
2003-09-02 21:43:08 » |
|
You guys will have to be a little more specific by what you mean. At the OS level it is one device for me so that's how I represent it. If there is something specific that you're talking about lemme know.
|
http://www.gregorypierce.comShe builds, she builds oh man When she links, she links I go crazy Cause she looks like good code but she's really a hack I think I'll run upstairs and grab a snack!
|
|
|
Games published by our own members! Check 'em out!
|
|
|
endolf
|
|
«
Reply #3 - Posted
2003-09-02 23:30:46 » |
|
Hi I thought I explained this, guess my explination was poor . The Mouse under windows and linux plugins is represented as one device, with two subdevices, one subdevice for the MouseBall and one for the MouseButtons, take a look at the classes net.java.games.input.Mouse and net.java.games.input.DirectInputMouse DirectInputMouse constructor constructs itself with a BallImpl and an ButtonsImpl, which extend Ball and Buttons from Mouse, these are the devices that actually have axes in them, DirectInputMouse doesn't, and for consistancy I did the Linux one the same way. That is what we mean by two devices, rather than one. Endolf |
|
|
|
|
gregorypierce
|
|
«
Reply #4 - Posted
2003-09-03 01:46:56 » |
|
Okay, and how is this different from what the OSX version does. What I need someone to say is 'here is what you did in the OSX version - could you do it like xxxx.' Without a clean spec, I just implemented it the easiest way for OSX.
|
http://www.gregorypierce.comShe builds, she builds oh man When she links, she links I go crazy Cause she looks like good code but she's really a hack I think I'll run upstairs and grab a snack!
|
|
|
|
endolf
|
|
«
Reply #5 - Posted
2003-09-03 09:07:50 » |
|
Hi
By my quick look at your code you did it the same way, I guess I'll answer Jeffs queston then, it looks like we have all done it as two devices MouseBall and MouseButtons
Endolf
|
|
|
|
|
Jeff
|
|
«
Reply #6 - Posted
2003-09-03 18:54:59 » |
|
Guess I was confused!
Sorry guys and thanks.
JK
|
|
|
|
|
gregorypierce
|
|
«
Reply #7 - Posted
2003-09-03 20:59:25 » |
|
That's how I kept getting confused because I couldn't understand what I had done differently as I'd simply followed the Windows code making modifications to the Impl classes to match what I needed for OSX. There is an OSX mirror for every DirectInput class |
http://www.gregorypierce.comShe builds, she builds oh man When she links, she links I go crazy Cause she looks like good code but she's really a hack I think I'll run upstairs and grab a snack!
|
|
|
|
swpalmer
|
|
«
Reply #8 - Posted
2003-09-06 22:45:50 » |
|
I checked in some build.xml files for OSX. They may benefit from some tweaking, but they seem to work. I based them on the linux versions.
|
|
|
|
|
endolf
|
|
«
Reply #9 - Posted
2003-09-07 08:29:04 » |
|
I based them on the linux versions. Well there is your first mistake Endolf |
|
|
|
Games published by our own members! Check 'em out!
|
|
|
swpalmer
|
|
«
Reply #10 - Posted
2003-09-07 20:46:10 » |
|
Ah, well if they cause problems blame Endolf |
|
|
|
|
kevglass
|
|
«
Reply #11 - Posted
2003-09-07 20:50:37 » |
|
Ah, well if they cause problems blame Endolf
Its always worked for me!  Kev |
|
|
|
|
endolf
|
|
«
Reply #12 - Posted
2003-09-07 23:02:03 » |
|
Thats right, blame poor innocent me. I've had enough, i'm gonna take my ball and go home |
|
|
|
|
kevglass
|
|
«
Reply #13 - Posted
2003-11-28 16:47:16 » |
|
Whats happening with the MacOS X port? I check the nightly builds and there don't actually appear to be any plugins for MacOS in the download gzip.
Kev
|
|
|
|
|
Jeff
|
|
«
Reply #14 - Posted
2003-11-29 18:35:28 » |
|
We had a problem with the OSX build machine for a few days.
It should be back up now.
|
|
|
|
|
endolf
|
|
«
Reply #15 - Posted
2003-11-30 18:59:03 » |
|
build dated the 30th still only had the linux c source, the DX dependancies and the core stuff.
Cheers
Endolf
|
|
|
|
|
swpalmer
|
|
«
Reply #16 - Posted
2003-11-30 23:26:25 » |
|
There are still a few issues with the Mac port:
OS X port is not working for game pads. It detected my iShock gamepad but the test code just generates an empty window for it with no controls.
Powerbook track pad is shown as having 2 buttons - likely apple's fault.
Powerbook keyboard qualifier keys (shift, ctrl, option(alt), command(meta)) don't work. Powerbook PG UP and PG DN keys (fn + cursor up/down) don't work, but HOME and END (fn + cursor left/right) do work.
Jeff, can you try the above stuff on your PB?
It appears that in general JInput can be used on the Mac now for mouse input, and with luck some keyboard input..
|
|
|
|
|
Jeff
|
|
«
Reply #17 - Posted
2003-12-01 05:11:37 » |
|
There are still a few issues with the Mac port:
OS X port is not working for game pads. It detected my iShock gamepad but the test code just generates an empty window for it with no controls.
Which, unless my test program has a bug, means its seeing the pad as a device but no axes on it. Have you tried the text test that just dumps to stdout what it finds?
Powerbook track pad is shown as having 2 buttons - likely apple's fault.
Yeah I saw that too.
Powerbook keyboard qualifier keys (shift, ctrl, option(alt), command(meta)) don't work. Powerbook PG UP and PG DN keys (fn + cursor up/down) don't work, but HOME and END (fn + cursor left/right) do work.
Jeff, can you try the above stuff on your PB?
Will do. Are you seeing no keybaord device on your PB liek I am on mine? It appears that in general JInput can be used on the Mac now for mouse input, and with luck some keyboard input..[/quote] |
|
|
|
|
Jeff
|
|
«
Reply #18 - Posted
2003-12-01 05:21:00 » |
|
Okay i take it back, i AM seeing the KB. (I dunno how I missed it last time).
All behavior confirmed.
A strange thing to add. Page Up and Page Down seemed not to be being grabbed by the lib (I had this window selected and they put garbage in it when pressed.)
|
|
|
|
|
gregorypierce
|
|
«
Reply #19 - Posted
2003-12-02 18:15:59 » |
|
Someone open up a bug and assign it to me and I'll deal with it.
|
http://www.gregorypierce.comShe builds, she builds oh man When she links, she links I go crazy Cause she looks like good code but she's really a hack I think I'll run upstairs and grab a snack!
|
|
|
|
