There are several functions which have been defined in the headers, where, these functions clearly require a string pointer, i.e. (LPSTR) Yet they have been defined as a DWORD!
This really needs to be looked at, because linking against such functions causes problems. For example, if I change the argument type from a DWORD to an LPSTR, the linker complains... Clearly because the overrided function doesn't exist.
Such functions are:
dbDLLLoad and dbLoadDLL. They have been declared as DWORD in the header files, which is wrong. I use these types to determine the type generated for the DGDK.NET toolkit. An LPSTR is converted and used correctly, where as a DWORD just screws things up. Remember guys, .NET uses UNICODE strings, where as the DGDK does not. So I use the types to automatically convert from UNICODE/non UNICODE and vice versa. If the types defined in the header are clearly wrong, it's making life....well.. difficult.
Please, could you guys sort this out
Thanks.
[EDIT] I've managed to get the DGDK.NET toolkit compiled against 1.6.2, but some of the functions fail. Reason is, the function was defined with a DWORD, and my conversion code does not understand this. If it's defined as an LPSTR, then it's interpreted correctly. Remember, I'm updating this tool for over 1400+ functions.
Paul.
Home of the Cartography Shop - DarkBASIC Professional map importer
