WEBINAR: On-demand webcast
How to Boost Database Development Productivity on Linux, Docker, and Kubernetes with Microsoft SQL Server 2017 REGISTER >
"Auto hide" feature is not implemented yet.
Source code is provided with a sample (MDI application generated by VB Application Wizard). Actual code (which should be ported to your application) is in following files:
- TaskBar.ctl - UserControl code
- Icon.cls - a class used for storing information about child windows handled
- Declares.bas - contains all necessary API related stuff.
As it was written, there are two major components: a control itself and an auxiliary class clsIcon. The TaskBar control uses some functions from API, declared in moduleDeclares and some module routines implemented there.
For each control an object of the clsIcon class is created and stored internally in the collection m_colIcons. All important changes (e.g. these, we carry about) to each window made by an user are thus reflected in the collection. Then the collection will be used (in UserControl_Paint event handler) to prepare buttons for each window.
There are no other controls placed on TaskBar control. Everything is painted "by hand" and all events (mouse up, down etc.) are handled by a code of the control. When an user clicks within control, program determines, which button is affected and then changes it's state (and look). I think, I implemented reasonable behavior. When a change made by user to a window affect only one button, only a part of the toolbar will be repainted (I use API InvalidateRect instead of VB's Refresh).
Operations of minimizing and restoring MDI windows are handled separately in order to achieve effect of "hiding" windows.
Class clsIcon stores all information necessary to paint a button for a specific window, including a reference to window's icon. It also has a feature (touch properties), which helps me to detect, which window has ben destroyed and is no longer present without performing separate iteration through Forms and icons collections to compare them.
The module contains all global API declares required and implementation of two crucial functions:
- the one, which subclasses MDIClient window
- new WndProc for MDIClient, which notifies UserControl about events among MDI Client children
How to Use That
Simply append these three files to your project and place TaskBar on your MDI Form. If you want to have context menu for taskbar and for child windows (right click on a button), you have to provide proper menu objects in handlers for events fired by this control.
- MDI TaskBar, as it is implemented can't exist as a separate ActiveX - the reason is it uses the Forms collection.
- You can't place additional buttons on the toolbar unless you will change all calculation related functions (ItemRect etc.).
- Although TaskBar may be docked vertically, it won't work properly if there are to many windows (it won't crash, but new windows won't be displayed).
- This cool "Auto hide" feature is not implemented yet.