I have a macro that works just fine with VS 12.
However, when I upgraded to VS 2009, the same macro threw this warning. However it seems to load after a couple of times..
Module <my macro> contains a call to '_tbAddForm' with an uninitialized variable. Declare a function prototype to find the error at compile time.
I dont understand how to go about creating a function prototype for this.
That does seem cryptic, especially without being able to see your code.
Perhaps if you post the code, it would be easier to offer a suggestion.
Also I saw that there is a Macro Debugger, but there seems to be no info on how to invoke it on my Macro.
Similar to if you were debugging a program:
1. Use the Macro|Start Slick-C Debugger... command to start the debugger.
2. In the debugger, set a breakpoint at the point where you want to start debugging.
3. In the main SE window, invoke your macro.
When the breakpoint is reached, the macro will break into the Slick-C debugger.