I'm using the following method to have a callback for TaskDialogIndirect... it works in VBA7 32bit, VB6 (32bit), twinBASIC 32bit, and twinBASIC 64bit, but crashes in VBA7 64bit (In all scenarios I'm testing the VBA7 method of calling it; I use a workaround that copies it into a UDT consisting of a byte array, to avoid the automatic padding that will break it otherwise. If I disable the callback, the API works, so it's definitely that).
Then in a standard module,
I put a MsgBox in the first line of the callback; it never enters it. cTaskDialog is the name of the class.
I'm at a loss to explain why this works in all scenarios except 64bit VBA.
Attaching the full .cls/.bas I'm currently using.
If anybody has a clue what might be going on... or an alternative method for class module callbacks that does work in x64, I could really use some help here.
Code:
uTDC.pfCallback = tdFARPROC(AddressOf TaskDialogCallbackProc)
uTDC.lpCallbackData = ObjPtr(Me)Code:
Public Function TaskDialogCallbackProc(ByVal hWnd As LongPtr, ByVal uNotification As Long, ByVal wParam As LongPtr, ByVal lParam As LongPtr, ByVal lpRefData As cTaskDialog) As Long: TaskDialogCallbackProc = lpRefData.zz_ProcessCallback(hWnd, uNotification, wParam, lParam): End FunctionI'm at a loss to explain why this works in all scenarios except 64bit VBA.
Attaching the full .cls/.bas I'm currently using.
If anybody has a clue what might be going on... or an alternative method for class module callbacks that does work in x64, I could really use some help here.
