Re: Combined build
> I think mech games should be left out as I always looked at them as a nusance.
Left out from what? Source code, binary?
The point is to make c ...
|
EmuChat
|
LazyCat
|
05/07/12 11:37 PM
|
Re: Combined build
>> Apparently you haven't seen what we've been doing at all. #ifdef MESS hasn't existed for well over a year now. There is one single object-ori ...
|
EmuChat
|
LazyCat
|
05/07/12 11:19 PM
|
Re: Combined build
>> If you look at what MAMEdev's actually shipping, you'll see that we've been converting the entire codebase from fake OO with macros to real O ...
|
EmuChat
|
LazyCat
|
05/07/12 07:47 PM
|
Re: Combined build
>>
It's as accurately representing the actual game state as much as possible. Thus why things such as MAMEHooker are supported, such as they are ...
|
EmuChat
|
LazyCat
|
05/07/12 07:39 PM
|
Re: Combined build
> Guess what? It already is. Drivers can be EASILY removed before compilation. There's
> no point in separating drivers out into, say, DLL files ...
|
EmuChat
|
LazyCat
|
05/07/12 05:37 PM
|
Re: Combined build
>>
LazyCat is almost certainly Abracadabra, if you remember that dude (Haze agrees with this analysis, for those of you who listen to him rather ...
|
EmuChat
|
LazyCat
|
05/07/12 05:23 PM
|
Re: Combined build
> Remove the Neo Geo games? All the artwork as well?Blasphemy! Glad you are not in
> charge
I understand your reason, let me explain mine.
I ...
|
EmuChat
|
LazyCat
|
05/07/12 05:08 PM
|
Re: Combined build
>>
Given that a majority of users (and devs) don't want the combined build, and that it would greatly increase bandwidth costs for MW and our ot ...
|
EmuChat
|
LazyCat
|
05/07/12 03:26 PM
|
Re: Combined build
>> you do know that what you says is *exactly* what MESS already does?
maybe you shall check what you're talking about, before posting
> how ...
|
EmuChat
|
LazyCat
|
05/07/12 02:53 PM
|
Re: Combined build
I believe you could have the best of both worlds. MESS and MAME can be united, yet become even more separated than before.
Why not have C64 or NES b ...
|
EmuChat
|
LazyCat
|
05/07/12 12:42 PM
|
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
I see you are surprised about re-write for what seems like a huge effort where there is no any personal gain, only I never told you what is my build r ...
|
Programming
|
LazyCat
|
04/29/12 12:51 AM
|
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
> I have stated the reason it was done, but you are free to agree or disagree as you
> see fit.
>
You said the reason was to make it univer ...
|
Programming
|
LazyCat
|
04/28/12 06:18 PM
|
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
> The port definition in the driver states the size, and MAME converts it. Why would
> you want to redo the work in 1000s of drivers?
>
> ...
|
Programming
|
LazyCat
|
04/27/12 06:02 AM
|
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
> It is the range passed from the OS layer to MAME which then gets converted to the
> port value needed by the game driver. Which can be anythin ...
|
Programming
|
LazyCat
|
04/26/12 07:13 PM
|
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
R. Belmont,
Except C/C+, what else is there to know? Surely you must have opinion on the subject regardless of whether or not you are aware of the cu ...
|
Programming
|
LazyCat
|
04/26/12 03:21 PM
|
Re: Why are MAME INPUT_ABSOLUTE_{MIN/MAX} 17 bits?
Bryan Ischo,
Please point me at what file(s) are you looking at and what variables? What data type is used to store that value?
I would expect the ...
|
Programming
|
LazyCat
|
04/26/12 01:41 PM
|
Previous
Main search page
