2.0

Clears a DLL from the messaging registry.

extern "C" void WINAPI VCClearAlertAppDll(short* iError, char* DllName, char* NativeCmd);

procedure VCClearAlertAppDll(var iError: Smallint; DllName: PAnsiChar; NativeCmd: PAnsiChar); stdcall;

Sub ClearAlertAppDll(ByVal DllName As String, ByVal NativeCmd As String)

DLLName - the name of the DLL to register.
NativeCmd - the native command name used to reference the tool operation.

An option introduced in version 2.0 of Visual CADD™ is to make tools and interfaces in dynamic link libraries (DLL's). This interface to Visual CADD™ provides all the functionality of the message based EXE tools that were used with version 1.x. Some advantages to DLLs over EXE are: a DLL shares the same memory space as Visual CADD™, once loaded into memory, a DLL will stay in memory until Visual CADD™ closes, code can be run on load and different code can be run each time a function is called, no interface or HWND are required, no checking is required to see if Visual CADD™ is running since it is the one calling the DLL, and several tools can be in one DLL without command line options necessary for EXE to achieve the same functionality.

Any tool is made up of several functions that handle each of the events passed by Visual CADD™. The old way was to use VCSetAlertApp to register a list of messages your user tool needed in order to function properly. This was limiting in many development languages like Visual BASIC because only certain controls could receive the needed messages and even those controls were limited by the number of messages they could handle. Even if all the needed messages were available they could accidentally be triggered if the interface was displayed on screen. Now, VCSetAlertAppDLL registers a group of exported functions in a DLL to be used instead relying on message handlers.

VCClearAlertApp, VCSetAlertApp, VCSetAlertAppDll