Main > Software Forum
MAME 104u5 out - adds multiple mice
<< < (5/15) > >>
Lilwolf:
I see Howards point (yet think it could have been mentioned in a nicer way).

I have 3 control panels that are hot swappable with mice on them.   And will probably have a lot more in the future.  I never do it ingame (because I switch my frontend to show the new control panel, it updates the games and the controls for the frontend... swap the control panel and go from there... ie, I can't select a game without first changing the control panel itself).

Here is the issue...

I have a control panel that plugs in and now 2 trackballs make a connection.  Will they always be recognized in the same order?   I haven't tried but I'm guessing they wont be.  But that might be based on the passive hub. 

And if I ever wanted to add a mouse to my system for debugging (that I leave in the cab) I better do it before I start setting everything up.

But after those things being stated.  I now CAN use MAME+XP and multiple mice.  And that is MUCH better then before.  Analog+ mame is great but very outdated.  And having real support gets me a giddy inside!

Anyway, can't wait to see the updates to the light gun games!   
Howard_Casto:

--- Quote from: Lilwolf on March 14, 2006, 10:59:37 am ---I see Howards point (yet think it could have been mentioned in a nicer way).


--- End quote ---

I'm not picking on you Lilwolf but how come the ONLY slightly negative thing I said was that the mmame devs were short sighted in the way they went about coding this was precieved as "unnice"?  Especially considering I get insults of my programming competancy, my tone, and that my opinon basically doesn't count, as well as wonderfully mature comments like "you are talking out the wrong end" spit at me just because one individual didn't like the fact that I didn't agree with the way they coded in their contribution. 

Is multiple mice in xp a good thing?  Of course, I'm glad to see it added.  Was it added the "right way"?  To steal a phrase, "oh hell no!"

Bad coding structure is bad coding structure I'm sorry some lower level devs get ther feelings hurt if you question their all-knowing directions with the project. 
jcrouse:
Howard,
      With all due respect, it IS your tone. It is ALWAYS your tone. The same thing you just pointed out to LilWolf you tun around and do to Derrick by calling him a low-level dev. That could be interperted as insulting and a judgement of his knowledge. Remember, we all have a common goal for the betterment of the emulation community.

John
Howard_Casto:
Exactly, which is why I'm the ONLY one who speaks up when bad code is being put into a good product. 

And for the record, I was referring to my ORIGINAL tone.  Once someone insults me, the kid gloves come off.  So yes, that was intentional.  So with respect, always look at the original conversation, and not the aftermath of someone trying to disrespect me, because I will put them in their place.  :)

There's no nice way to say something is being done wrong to some who thought they were doing good.  Sad, but true. 

But as a gesture of good faith, I would suggest looking at the cpnmouse api (probably not the best method for mame).  And my personal favorite, hooking the wm_input data at a low level, which you can marry with the direct input function to do things exactly as I described... basically linking direct inputs mouse enumeration with the data functions so you can tell which device, not just with device number.  For that matter you can do it just as easily if not easier with rawmouse, but it isn't being done because our dev has decided he knows what's best for us. 

I know the trend right now is to remove optional flags from the mame code, unfortunately that is a very BAD trend.  The problem with it is that leaving the options in doesn't hurt anything and taking old options out usually throws a good percentage of the population out to the curb, looking for other solutions.  Like when Aaron took out the -list details flag, which several fe devs (including myself) depended upon.  Mind you I found an alternate route to get the data, but it requires a fair bit of hoop jumping and I doubt leaving the very small list details function in the mame source would have been the end of the world. 
Derrick Renaud:

--- Quote from: Howard_Casto on March 14, 2006, 06:23:42 pm ---mature comments like "you are talking out the wrong end" spit at me just because one individual didn't like the fact that I didn't agree with the way they coded in their contribution. 

Is multiple mice in xp a good thing?  Of course, I'm glad to see it added.  Was it added the "right way"?  To steal a phrase, "oh hell no!"

Bad coding structure is bad coding structure I'm sorry some lower level devs get ther feelings hurt if you question their all-knowing directions with the project. 

--- End quote ---

I stand by my "wrong end" statement.  You have stated that both DX and RAWMOUSE are the wrong way to go.  Yet offer nothing.  That is talking out the wrong end my friend.  If you have this magical knowledge about the best way to access individual mice, then put up, or shut up.

I could care less if you like my contribution.  What I don't like is how you state MAMEdev erred, and that I erred in the code.  Offer no proof.  State things that are completely false, have it refuted, and only offer, "I'm still right" as proof.

Any bad coding structure in RAWMOUSE is forced upon you by Microsoft.  Such as how new mice are added as the first item in the list.  But again please enlighten me on my bad coding skill.  But then like all your statements, you just spit them out and can not back them up.

I am always Man enough to admit when I am wrong, and will publically do so once you offer some proof of this better way.

Otherwise, we will have to leave it as differing opinions from someone who has coded something that works.  And someone who possesses great unspoken knowledge.

D.
Navigation
Message Index
Next page
Previous page

Go to full version