NextGen Integer, Pointer, LongPtr etc
It maybe too soon to ask this but just to clarify
If we have an external function call like this
Code:
External_Function WinAPI_GetTempPath "GetTempPathA" Kernel32.Dll Dword nBufferLength Pointer lpBuffer Returns Dword
For Next Gen does Pointer need to be LongPtr or will the compiler do this automatically depending on 32/64 bit compile ?
If for some reason I had a pointer value in a local integer that I was going to pass to this then this would need to be changed to Pointer or LongPtr or even Address ?
Had lpBuffer been an integer I assume it would need to be changed to Pointer/LongPtr/Address ?
Structs need to be checked to see if additional elements are needed wen doing a 64bit compile (see tWinStructs for examples)
If any datatypes needed changing for interacting with 64bit COM components I assume FlexCom would handle this if we use it to recreate the cCom.... wrapper class ... not that I can see any Pointers in our existing ones so maybe COM lives on an Integer only diet ?
Windows Notifications are you talking about WM_ window messages ?
Success consists of going from failure to failure without loss of enthusiasm - Winston Churchill