by Rachael » Fri Jul 03, 2009 3:19 pm
Graf Zahl wrote:The fact that Randy went crazy and renamed some variables just for the sake of it will also delay a new GZDoom update by at least another day.
I've already fixed the renderer issues if that's what you're referring to. The problem that I have with merging the code was the joystick code. I doubt you would, but you're free to use my merge-in if you want. It's available here:
http://svn.drdteam.org/experimental/gzd ... M.diff.bz2
If you do, though, I would strongly urge you to look at the joystick code. Also, don't forget to add the file src/win32/i_xinput.cpp - if it is missing, you will get a linker error. You'll also have to add it to gzdoom.vcproj.
I'm sure the vcproj file is updated in the diff, but I'm not sure if the i_xinput.cpp is, now that I think about it I don't think so.
[quote="Graf Zahl"]The fact that Randy went crazy and renamed some variables just for the sake of it will also delay a new GZDoom update by at least another day.[/quote]
I've already fixed the renderer issues if that's what you're referring to. The problem that I have with merging the code was the joystick code. I doubt you would, but you're free to use my merge-in if you want. It's available here: http://svn.drdteam.org/experimental/gzdoom-r1701-base-r375M.diff.bz2
If you do, though, I would strongly urge you to look at the joystick code. Also, don't forget to add the file src/win32/i_xinput.cpp - if it is missing, you will get a linker error. You'll also have to add it to gzdoom.vcproj.
I'm sure the vcproj file is updated in the diff, but I'm not sure if the i_xinput.cpp is, now that I think about it I don't think so.