* correcting x64 configurations to actually use x64
defining NOMINMAX to fix std::max error
* more preprocessor definitions for x64
* 64-bit libraries from the last published version of DXSDK with dinput
* should define WIN64 as well? unfortunately seem to require retention of WIN32
* added an x64 build of luaperks.lib, this compiles links and runs now
* relocate win32 luaperks.lib to src/drivers/win/lua/win32 and leave a note explaining it
* luaperks.lib x64 needed to be /MT
two more missing x64 libs
debug x64 configuration was set to compile C++ as C?
* importing the rest of the usable WIN32 preprocessor defines, debugger now functions!
* revert unnecessary VS solution version change
* 64-bit lua working (fixed the 64-bit build of luaperks.lib)
* VSUIENTRY hashes are unsigned, not signed
* more hashes that are actually unsigned
* fix a few pointer to int casts in lua console
* fix a few more pointer truncations in windows dialog stuff
a few printf arguments need a cast to int
* explicit size_t cast to quiet spurious warnings on an inline function
2. As bbbradsmith in Pull Request #62 mentioned, SetWindowLong is replaced by SetWindowLongPtr for 64 bit compatible, I partially changed those written by myself.
2. Fix a bug, when the cheat editing controls lost focus, but editing mode is still there, which makes case EN_UPDATE triggered when user is not typing in them, that's an inappropriate circumstance. It might make the cheat editing control shows nothing when selecting a cheat.
3. Re-arranged some controls in resource file.
4. Changed some directory dialog logic, use defined ID rather than hard-code the actural number.
5. Detail.
2. Add text limit to Memory Watch for experiment.
3. Make the IDs of controls in Memory Watch predefined rather than directly coded, that's not quite standard in programming. Calculations to ID is not always trusted as they are automatically determined by the development tool.
2. Add text limit to Memory Watch for experiment.
3. Make the IDs of controls in Memory Watch predefined rather than directly coded, that's not quite standard in programming. Calculations to ID is not always trusted as they are automatically determined by the development tool.
2. Separated cheat code and game genie in Cheat window.
3. Don't show a game genie code when affected address is under 0x8000.
4. Detail: set font for some edit control, replaced some static global variable.
5. Other details.
By the way, why there're so many useless brackets in some functions?
zeromus