TimoSoft TabStrip
1.10.5.184
|
TabStrip is an ActiveX control that wraps the SysTabControl32
window class. It is optimized for Visual Basic 6.0, but should also work in any other environment that supports COM controls.
The control superclasses the native tabstrip window class of Windows: SysTabControl32
. Although I tried to wrap all features of this window class (status: Windows 10), some things may be missing. In these cases you usually may use the Win32 API and handle the control as a native tabstrip window. One of my goals was it to create a tabstrip control that may be controlled via API as well as via the classes that I implemented.
TabStrip Unicode runs on the following operating systems:
Some features have additional requirements which are mentioned in the affected feature's documentation.
Limited support means, that I won't invest much work to support those systems. If a feature works on a system marked with "limited support" - fine; if it does not and it's easy to fix, I'll fix it, but if it's difficult to fix, I probably won't fix it. Also I will test the control much less on those systems.
There's no entitlement to support. Period. However, you have good chances to get help if you post your questions on GitHub or in the forums.
Also the project is open source, so feel free to have a look at the source code. You may modify it, but please consider sharing your changes with the rest of the world.
MIT License
Copyright (c) 2006-2019 Timo Kunze
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Thanks go to:
1. Why is the Font
property ignored?
It isn't. My controls have a property UseSystemFont
which defaults to True
. This property tells the control to use the system font rather than the font set by the Font
property.
Why is this property's default True
? Well, if I set system wide settings (like fonts) I expect all applications to follow them. Unfortunately ignoring system wide settings seems to be trendy, so see my decision as an educational measure.
2. Why is event xyz not fired?
Firing an event is relative time-consuming, even if the event isn't handled by the application at all. Therefore I implemented a DisabledEvents
property which can be used to deactivate certain events.
By default many events are deactivated.
3. The control doesn't seem to have full Unicode support if it is used in Visual Basic 6. Why?
The forms, that Visual Basic 6 is creating, are ANSI windows. Therefore they force the control's underlying native tabstrip window class to use ANSI messages when communicating with the form. This breaks Unicode support in some situations. To work around this problem, the WM_NOTIFYFORMAT
message needs to be reflected back to the control.
In Visual Basic, you have to subclass the control's container window and send WM_NOTIFYFORMAT
back to the window that it was sent for. In C++, message reflection works similar. The sample projects teach you how to reflect the message.
4. The control has drawing glitches if it sits inside a Visual Basic 6 Frame control and the app is themed!
The intrinsic Frame control of Visual Basic 6.0 doesn't work well with Windows themes. The drawing glitches you see are more a problem of the Frame control than of the TabStrip control. So far I have not found any work-around for the drawing glitches, that doesn't come with other side-effects like extreme flicker on control resize.
Until a better solution is found, you should make sure that you always place the TabStrip control inside a container which has its own device context (it should have a hDC property then).
Adequate replacements for the Visual Basic 6 Frame control are the Frame control from my ButtonControls library and the PictureBox control, depending on your requirements.