Subclassing and Hooking with Visual Basic

Some Subclassing Tips

As we’ve seen, subclassing involves creating a particular kind of callback function, one that is called by a window’s event loop. Hence, the general tips that we’ve presented for callback functions (such as defining the callback as a Public function in a BAS module and using On Error Resume Next for error handling in the callback function) apply as well to subclassed window procedures. In addition, though, two tips and pitfalls that are unique to subclassing are worth mentioning.

First, remember that all messages for a window are passed through its subclassed window procedure. As a result, the subclassed window procedure (as well as a hook’s filter function) can potentially be called hundreds or even thousands of times per second. If large amounts of code are executed in the window procedure for many of the messages, the performance of the application will degrade considerably. This makes it critically important to avoid doing too much work within a callback function. Performing file I/O in either type of procedure is one type of operation that could take up an unusually long amount of time to finish because of relatively slow disk access. If such long processes are included within these callback functions, the results could be less than satisfactory.

Tip

Do as little work as possible in the subclassed window procedure.

Second, never use the DoEvents function inside the window procedure. DoEvents will halt processing to allow other queued messages to be ...