The Ultimate Toolbox Home Page

• Download the Ultimate Toolbox source code - 3 MB
• Download the Ultimate Toolbox sample projects - 5.4 MB
• Download the Ultimate Toolbox documentation in compiled HTML help (CHM) format - 4.9 MB

Introduction

Welcome!

We are very happy to announce that we have made the decision to offer our commercial lineup of MFC libraries, including Ultimate Toolbox, Ultimate Grid, and Ultimate TCP/IP to The Code Project community free of charge.

These are the full and complete libraries including source code, documentation, samples and examples.

Ultimate Toolbox, Ultimate Grid and Ultimate TCP/IP come with full source code, and are compatible with Microsoft Visual Studio versions 6.0 through 2005.

The Ultimate Toolbox and line of related MFC libraries products have been powering professional MFC applications for more than 10 years. We realize that there is a very large number of users who are still coding new applications in Visual C++ and MFC and who are looking for effective and proven libraries to enhance their applications, as well as those with legacy code to maintain and update.

By releasing these long standing MFC libraries to The Code Project community we hope that the libraries will continue to grow, evolve and provide a library of useful controls to the development community through the auspices of The Code Project and its members.

Contents

• Categories
• Features
• Configuration
• Getting Started
• Community Support
• Licensing
• History
• Comments

Categories

The Ultimate Toolbox forms an extensive collection of classes dealing with many aspects of Windows programming. We have organized the samples and documentation into the following categories - each category page lists the main classes available in that group, and some will contain a link to sample accompanying short article. (Note that most of these are short overviews distilled from the existing documentation - for full class references, refer to the compiled HTML help documentation download.)

• Application Customization Framework
• Application Skins (Office XP and 2003 'look and feel')
• Communication
• Database
• File Management
• Graphics
• Graphics Formats
• Graphical User Interface
• Intellimouse
• MAPI OLE
• Shell
• Utility
• FAQ
• Updates and User Contributions

Ultimate Toolbox Features

Extended MFC UI Controls

Controls that we derived from existing MFC controls and improved upon. These include components such as:

• Office 2003-like and Office XP-like look and feel
• Shortcut bars.
• Extended combo boxes.
• Extended tree controls, including an option tree.
• Masked edit controls - generic and specialized

Classes Extending the MFC UI Framework

These classes expand upon the document-view framework, and provide enhanced functionality such as:

• Customization classes that let your users customize the UI of your application (e.g. the creation/modification of toolbars, menus, etc.).
• Cool tool bar classes, letting you easily add controls to your toolbars (drop lists, check boxes, edit controls, etc.).
• Cool menus, like cool toolbars, allow you to quickly provide advanced functionality to your menus (e.g. display icons/bitmaps).
• Docking windows classes that give your docking windows the functionality and feel of Microsoft applications (e.g. Office 2000).
• Tab view classes that let you display tab views using a wide variety of styles, such as Hot Track, Multi-line and Positioned (left, right, etc.) tabs.

Utility and Shell Extension Classes

These classes can enhance your applications by letting you retrieve system information, implement trace/debugging features, use sound effects, and perform other utility-related operations with ease. Examples of these utility and shell extension classes are:

• A system information class.
• Advanced trace and assert classes.
• Sound effects class.
• XML file parsing class.
• Resource file modification and view classes.
• Data Compression class
• Task bar and Application bar classes.

Graphics Classes

These classes let you display graphics (e.g. BMP, JPEG, etc.) with ease, and the kit also comes with JPEG compression and metafile creation/playback classes. Some examples are:

• JPEG compressor and de-compressor libraries.
• DIB manipulation/conversion classes.
• Metafile classes that come with Ultimate Toolbox provide functionality to load all standard formats of Metafiles (*.wmf, *.emf) from either disk or resource, play back loaded metafiles, and even create new ones.

Configuration

Layout

We've split up the code, samples and documentation of the Ultimate Toolbox into separate ZIP files, to make updates easier.

In general, for a code library such as the Ultimate Toolbox, installation files are a cumbersome nuisance. While they do allow the formality of license agreement acceptance, and are expected of a commercial offering, for our purposes it would be too much trouble to update an entire install in order to accommodate a small update to a core source file or sample - we may in the future provide updates in various formats, from a single class to an entire new distribution as situations warrant. And, of course, the CP community is more than welcome to contribute.

The samples and library projects all reference relative paths with respect to source and include files, and should compile 'out of the box' if the ZIP files are extracted to a common directory - by default, Ultimate Toolbox, which should look more or less like this:

Getting Started

Once the main source and sample distribution is installed, you'll find that most of the samples can be built and run without the need to build any libraries or DLLs. This source code download has been stripped of some of the pre-built libraries that were shipped with previous commercial installations in order to conserve bandwidth - notably the proprietary JPEG libraries, which should be built ( Ultimate Toolbox\lib\JPEG\jpg.dsw ) before building the samples that reference it and the static libraries or DLLs. The jpg VC6 workspace should convert and build without problem with Visual Studio .NET or 2005, and the resulting libraries placed in the Ultimate Toolbox\lib\Libs directory. The static libs and DLL builds in the lib\Build Libs and lib\Build DLLs can then be built.

The static library is handy when using one of the frameworks (docking windows or app customization), but many classes can be easily used directly in your project with the addition of only one or two source and header files - season to taste. For the most part, except for samples that show the use of the DLL or static lib, the samples use the source directly allowing for direct debugging and testing as the need arises.

The CHM DOC file will provide more detailed information on each of the classes and their interfaces, and has an index and full text search - great for 'hmmm... I wonder if there's a class for...' type scientific explorations.

Community Support

Support for the products will be community based, and will include participation from core developers of the products, long standing and informed users of the products, and other members of the CodeProject.com community.

Licensing

It is our intention that you be able to use the libraries in any manner you wish, however, specific details of licensing rights, limitation of liability, and other details are included both here, and in a license.txt file included with the downloadable packages

History

August 2007 - Ultimate Toolbox Version 9.3 forms the initial CodeProject community release.

Version 9.3

New:

• The Hyperbar classes provide an easy way to add some cool UI functionality to any existing or new project that uses a toolbar.

Bug Fixes:

• Missing VS2003 static lib build project files reinstated.
• Vista problems with 'shadow window' rendering addressed.
• OXSkins - it's now possible ( and preferred ) to specify the desired skin using an enum
• The CustomiseManager sample has a minor bug fix, which caused a very rare crash
• OutlookStyleDemo : Added ability to change skin type at runtime, and improved overall skin support.
• COXBItmapMenu : Fixed bug which caused documents to close when dirty without prompting
• COXFrameWndDock::MakeItDockable : Can now specify which sides to support and if we should dock immediately
• COXFrameWndDock::AttachMDIChild : Allows users to specify the side to dock to, before it would dock to the first one that was available. Also fixed some docking bugs in this class.
• COXListEdit : Added code to send a message to indicate editing has ended when the drop button is pressed.
• COXPropertyTree : Added code to send a message to indicate editing has ended when focus is lost.
• Moved all the skinning drawing into seperate classes, so they are all handled polymorphically by the toolbox controls.
• COXSizeDockBar::TabAllDockedControlBars : Added code so that the visible bar can be selected, via a pointer or by index.

Version 9.2

Major release feature:

• The entire code base is now compatible with VC++ 2005, VC++ 2003, and VC++ 6. You get zero-warning compilation on VC++ 2005.

Bug Fixes:

• COXComboPickerCtrl::OnPaint now checks if the OS version is XP or higher, and if so it uses the default OS painting, else it does custom painting for the combo box arrow
• COXCalendarPopup::OnPaint : A bug (missing cast) has been fixed which caused an error in VC++ 7.1 or higher
• COXDateTimeCtrl::OnDropDown : The return value has been changed from TRUE to FALSE, thus fixing a bad bug where the parent window never gets to handle the notification.
• The bug in MDI child menus (in skinned mode) where the restore, minimize, and close items were shown in an un-skinned condition has been fixed.
• COXSysInfo has been updated to correctly identify all OSes up to Windows Vista.
• The Cool Controls demo had a bug where the Listbox tooltips came up as garbage - this has been fixed.
• Minor bugs have been fixed in the Status Bar demo (which caused garbage to show up in it)
• The Screen Grabber demo has been fixed to not crash on a multiple monitor setup.
• A trivial bug in COXMDIFrameWndSizeDock::OnActivate has been fixed.
• A bug in COXTreeCtrl that caused random crashes during drag/drop scenarios has been fixed.

Version 9.0

Major Upgrades:

1. The Office 2003 Look and Feel was added. The following Ultimate ToolBox UI elements support this new skin:
   1. Menus
   2. Toolbars and menubars
   3. Docking windows
   4. MDI tabs and Tear-off tabs
   5. Shortcut bar
   6. Properties window
   7. Status bar

2. The Properties window was enhanced to look more like the VS.NET properties window.

Minor Changes and Fixes:

1. A bug causing the Caption Painter not to work in Windows XP was fixed.
2. A problem casing excessive flashing of the toolbar, menu bar and docking windows under the Office XP skin was fixed.
3. A problem causing the close, minimize and maximize buttons of the menu bar to appear too large in skinned Windows XP was fixed.
4. A bug causing a floating toolbar to stick to the mouse cursor even after the user has released the button was fixed.
5. A GDI leak found in the Office XP skin causing problems in Windows ME was removed.
6. Several upgrades to the COXTreeCtrl were implemented:
   1. Arrow key navigation was added.
   2. Various drawing problems involving different back colors were fixed.
   3. An item indentation problem involving adding a child item to a collapsed parent was fixed.
7. A problem in COXPreviewDialog caused by a font that does not exist in all operating systems was fixed.
8. The classes COXTreeCtrl and COXGridCtrl will draw their sort headers correctly now in Windows XP skinned mode.
9. Several upgrades to the COXPropertiesWnd class were implemented:
   1. OnDeleteProperty() notification was added.
   2. A method for deleting all properties called DeleteAll() was added.
   3. A problem causing a crash if a property is deleted while being edited was fixed.
   4. A problem causing the combo box drop list not to show in its entirety was fixed.
   5. Added the following functionality: when editing a property the changes will be accepted if Enter is pressed and discarded when Escape is pressed.
10. Fixed a problem in COXMultiComboBox causing uncontrolled scrolling to the bottom of the drop list in Windows XP skinned mode.

Sample Changes:

1. The SkinsDemo sample was enhanced to show the new Office 2003 look and feel.
2. The SkinsDemo sample was upgraded to demonstrate how to show and hide the different docking windows from the View menu.

New Classes:

1. COXUxTheme – internal class used by various Ultimate Toolbox classes designed to detect the presence of Windows XP skins and retrieve their color schemas.

Version 8.1

Major Upgrades:

1. Visual Studio.NET 2003 full compatibility.
2. Enhancements to the VS.NET like properties window: the following property types with their appropriate editors are now supported:
   1. Text
   2. Numeric (with the ability to specify the number of decimal places)
   3. List of items (enumeration)
   4. Date
   5. IP address
   6. Currency
   7. Color
   8. Filename
   9. Directory
   10. Time (from nanoseconds to days)
   11. Angle (degrees, radians or grades)
   12. Length (metric or imperial)
   13. Temperature (Celsius, Fahrenheit, Kelvin)
   14. Custom field with a custom editor.

Minor Changes and Fixes:

1. The TVOXS_NOFOCUSRECT style was introduced in COXTreeView to provide the ability to turn off the item focus rectangle for selected items.
2. A buggy assertion statement was removed from COXMDIChildWndSizeDock::Create(…)
3. An auto-scrolling problem in COXMultiComboBox was fixed.
4. A bug in COXPhysicalEdit causing a crash was fixed.
5. A bug causing all drop edit controls to show garbage characters in the tooltips was fixed.
6. A bug preventing COXTreeCtrl::SelectItem(…) from having any effect in single selection mode was fixed.
7. A bug causing a floating menu to jump away from the mouse cursor was fixed.

Sample Changes:

1. The SkinsDemo sample was enhanced to demonstrate the use of COXPropertiesWnd and all the different type of properties that are supported.
2. The CustomizeManager sample was modified to reflect that in CMainFrame::OnCreate() InitializeToolbars() must be called prior to calling InitializeCommands().

New Classes:

1. COXPropertyTree – internal class used by COXPropertiesWnd.
2. COXListEdit – A drop edit control with the ability to display a list of items.
3. COXListPopup – internal class used by COXListEdit.
4. COXIPEdit – A an IP address edit control.
5. COXCalendarEdit – A drop edit control for dates.
6. COXMonthCalPopup – internal class used by COXCalendarEdit.

Version 8.02

Changes and Fixes:

1. When the snapping and tear-off behavior is enabled a floating window could not be resized. This was fixed.
2. OXShdWnd.cpp was not added to the build library project causing link errors. This was fixed.
3. In COXPropertiesWnd it was possible to edit a category name, which caused a crash. This was fixed.
4. When the extended tree control (COXTreeCtrl) is automatically populated the user could not expand the tree by single clicking on the plus. This was fixed.
5. Some painting problems of the edit control of the extended tree were fixed.
6. A problem preventing a date item from being edited in the extended tree was fixed.
7. The COXShdWnd class was not declared as exportable, which caused some link errors. This problem was fixed.
8. In the Customize Manager it was possible to turn off the "cool look" of the toolbars while in OfficeXP skin mode, which caused a crash. This problem was fixed.
9. A paining problem of COXCustomTBComboBox with the CBS_DROPLIST style under the Office XP skin was fixed.
10. A problem causing COXSkinnedCombo not to send CBN_SELCHANGE message was fixed.
11. A problem causing a floating window not to redraw the window behind it fast enough while moving was fixed.
12. In COXDao the FindNext method will work properly with searches on string values.

Sample Changes:

1. A new sample called CustomizeManager was added to the samples/advanced/ directory. This sample demonstrates how to use COXCustomizeManager. The different steps required are written as comments in the source code. Just search for the string "STEP".
2. A new sample called ExtendedTreeControl was added to the samples/gui/ directory. This sample shows how to achieve the functionality of COXTreeCtrl demonstrated in the downloadable Demo Browser.
3. The link errors in the TabViews sample were fixed.

Version 8.01

New Functionality:

1. Ability to programmatically tab all docked windows on a dock bar. Use COXSizeDockBar:: TabAllDockedControlBars(…) to accomplish this.

Changes and Fixes:

1. COXSkinnedComboBox now sends proper notification messages.
2. A combo box custom toolbar button is now properly centered in the Windows XP skin.
3. A behavior problem was fixed when the user double-clicks the gripper of a tabbed docking window.
4. A behavior problem was fixed preventing the user from moving a docked toolbar to the left edge of the windows without the toolbar going into float mode.
5. A crash in COXPreviewDialog which only occurred in Windows 2000 when compiled with VC7 was fixed.
6. Missing files causing links errors were added to the SideBySideToolbars sample.

You must Sign In to use this message board.

FAQ    Noise Tolerance Very HighHighMediumLowVery Low   Layout Expand Posts & RepliesThread ViewNo JavascriptNo JS + Preview   Per page 102550

Msgs 1 to 25 of 501 (Total in Forum: 501) (Refresh) FirstPrevNext

TABBED MDI miqel 2:53 15 Sep '09   I'd like to have closeing 'X' on each tab in tabbed mdi app. Any hint where i should start, making changes? Sign In·View Thread·PermaLink Re: TABBED MDI Tim Deveaux 9:07 15 Sep '09   Hi The paint code starts in COXSkinnedTabCtrl::OnPaint() and calls the draw code for the relevant tab skin - the COXTabSkinClassic::OnPaintTabCtrl method calls the default CTabCtrl processing, adding a bit if the tabs are themed or vertical. The COXTabSkinXP and COXTabSkin2003 OnPaintTabCtrl methods handle all the drawing, but I think they rely on the CTabCtrl to set up the size of the tabs, since they're not adding anything extra like a close button. Might be best for testing to truncate the text rect and use a DT_END_ELLIPSIS style then call a modified DrawCloseButton (see calls in the dockbar skins code). If you can get past the drawing revisions, I think you'll then have to add some button handling to the COXSkinnedTabCtrl class to act on a click to the close rect. Looks like a lot of work. Nice feature option though - might be especially useful for a COX3DTabViewContainer on a dialog or form. Tim Sign In·View Thread·PermaLink COXParser bug when decoding literal nbsp Member 4656294 7:08 5 Sep '09   When making a parse an xml and the value of an element contains the character the parser does not decode properly. Example Before: value&nbsp;-&nbsp;home After: value-house Note that the spaces are gone. Therefore Obeserver the solution to this problem is the function COXParser::InsertEntityValue       LPCTSTR lpszSeek=lpszEntity;    TCHAR chSpace=TEXT(' '); <-- Incorrect Check    while(*(lpszSeek) &amp;&amp; *(lpszSeek)!=m_chEndDelim &amp;&amp; *(lpszSeek)!=chSpace)    {       str.Append(*lpszSeek);       lpszSeek++;    } Am I correct in my explanation? Tks Alandy Sign In·View Thread·PermaLink COXSysInfo 64bit urd_sheir 0:04 13 Aug '09   hi I am working on 64 bit application. Your library is very good but I am wondering if COXSysInfo could be available on 64bit. I understand that due to inline assebmly cpuinf library is not available but is there any work around. Is there any other way? Currently I need memory functions (But may be in future I need other as well) GetFreePhysicalMemory GetFreeVirtual Please suggest some solution Regards Ayaz Sign In·View Thread·PermaLink Re: COXSysInfo 64bit Brett Rowbotham 22:33 30 Sep '09   I have a version of COXSysInfo that works in 64 bit. I haven't yet had time to pack up all the relevant files for posting here but if you PM me an email address I will zip and email you the files I have. Cheers, Brett Sign In·View Thread·PermaLink Bugs in COXMulticlipboardDlg::OnChangeCbChain [modified] Doodles 8:50 21 Jul '09   This is the body of COXMulticlipboardDlg::OnChangeCbChain: CDialog::OnChangeCbChain(hWndRemove, hWndAfter); //if the window we currently passing //notification messages changes, update //our handle if (hWndRemove==m_hWndNext) m_hWndNext=hWndRemove; //pass message to the next window if (m_hWndNext) ::SendMessage(m_hWndNext,WM_DRAWCLIPBOARD, NULL, NULL); First of all, the line that sets m_hWndNext=hWndRemove does nothing. I believe it is supposed to set it to hWndAfter. Second of all, the last line sends the wrong message. And it always sends it, even though it should not bother sending a message if hWndRemove==m_hWndNext was true. The corrected code is: //CDialog::OnChangeCbChain(hWndRemove, hWndAfter); //if the window we currently passing //notification messages changes, update //our handle if (hWndRemove==m_hWndNext) m_hWndNext=hWndAfter; //pass message to the next window else if (m_hWndNext) ::SendMessage(m_hWndNext,WM_CHANGECBCHAIN, (WPARAM)hWndRemove, (LPARAM)hWndAfter); (I commented out the base-class call because this routine does everything it has to, and who knows if the base-class call does something unexpected.) If these changes are not made, the results could crash your program and corrupt the clipboard-viewer chain. modified on Tuesday, July 21, 2009 2:08 PM Sign In·View Thread·PermaLink COXColor mluri 7:17 26 Jun '09   There's a class, COXColor, described in the documentation, but I cannot find it anywhere. Does it exist? I was going to create my own, then remembered, "Hey, I've got that cool library; maybe it's got what I need" and the docs say it does, but it seems it doesn't. So, does it exist? Where can I find it? Thanks Sign In·View Thread·PermaLink Re: COXColor Tim Deveaux 13:34 26 Jun '09   Definitely missing in action as far as I can see - I've asked someone to check the archive. Tim Sign In·View Thread·PermaLink Compile error! Help me!! [modified] stels000 2:07 2 Jun '09   When Allsample program compiled, Error!! --------------------Configuration: ActiveDesktop - Win32 Debug-------------------- Compiling resources... D:\MFC 그래픽 클래스\UltimateToolbox93_samples\Ultimate Toolbox\samples\shell\ActiveDesktop\ActiveDesktop.rc(289) : fatal error RC1015: cannot open include file 'UTSampleAbout.rc'. Error executing rc.exe. ActiveDesktop.exe - 1 error(s), 0 warning(s) Please,help me!!! modified on Tuesday, June 2, 2009 7:42 AM Sign In·View Thread·PermaLink Re: Compile error! Help me!! Tim Deveaux 6:37 2 Jun '09   It looks like you might not have unzipped the samples and source downloads into the same directory - they should share the same top level dir so that the relative paths are correct for the resource and include directories for the projects: Ultimate Toolbox archive include lib samples source You could probably just move the samples and archive dirs to the other Ultimate Toolbox dir to fix this - and don't forget to apply the updates[^]. Cheers Tim Sign In·View Thread·PermaLink Drag & Drop JRCooper 7:00 25 May '09   Hello, I am developing a MFC application using VC++2003. I can successfully drag & drop a file name, onto an edit control, using Explorer. However, I cannot drag & drop a file name, onto an edit control, when I use a CFileDialog box. Does the UT Toolbox have a custom CFileDialog box that support this drag and drop functionality? Thanks, -jc Sign In·View Thread·PermaLink 1.00/5 (1 vote) Skin colors jung-kreidler 1:06 25 May '09   Hi all, does anybody know how to change the coloring of a skin? The color for Office2003 skin is some kind of blue. Is it possible to change it to e.g. gray? Regards, jung-kreidler Sign In·View Thread·PermaLink Re: Skin colors JRCooper 6:53 25 May '09   Hello, To change the skin color, right-click on the desktop and select the "properties" menu option. Then select the "Appearance" tab. Next, select the "Color scheme:". The default color scheme is blue. -jc Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: Skin colors jung-kreidler 21:04 25 May '09   Default... that's why I asked for a coding way... Sign In·View Thread·PermaLink Re: Skin colors Tim Deveaux 6:28 26 May '09   I think if you vectored the calls to ::GetSysColor to a method of your own and had colors set up for the defined colors you want control over (COLOR_BTNSHADOW, COLOR_MENUTEXT, etc.) you could make some headway. Might even arrive at an extention that would allow some 'sub-theming' - could be useful. Haven't tried this tho - could be I'm missing something. Tim Sign In·View Thread·PermaLink Is SDI use possible? Sabuncu 9:59 18 May '09   The tutorial in the chm documentation file starts with creating an MDI project. Is it possible to use the UG in an SDI application? Thank you, Todd Sign In·View Thread·PermaLink Re: Is SDI use possible? Tim Deveaux 10:13 18 May '09   Yes, of course - the Basic example in the Examples dir uses an SDI - the code added to the view class should be pretty much the same as that for an MDI. Tim Sign In·View Thread·PermaLink Re: Is SDI use possible? Sabuncu 10:55 18 May '09   Thank you so much for the quick response, Tim. Your attending to the forums here is invaluable, much appreciated. Todd Sign In·View Thread·PermaLink Need help on Dock Bar nick2reg 2:49 18 May '09   I'm using the Ultimate Toolbox Library, and working with the SkinsDemo example of the library distributed packages. It's just great, but i have two questions: 1- The original example using TabAllDockedControlBars() to group FoldersBar and the PropertiesBar on a Tabbed bar at the right of the main window. But at the initialization, the Tabbed bar was minimized to the right border, and nothing shown. If I remove the TabAllDockedControlBars(), three bars are shown, but not tabbed. So why? and how to init it at a specific size ? 2- Now I have 3 FolderBar(s), and want to arrange them in one colunm, three row at the right of the main window. And three bars must be calculated automatically to have the same size (or heigh). So what I have to do? Please help! Thanks and Regards! Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: Need help on Dock Bar Tim Deveaux 9:39 18 May '09   Hi My first thought is that 1) may have been addresed in the first update, so want to check first if you've applied the updates[^]. Tim Sign In·View Thread·PermaLink Does this compile for Windows Mobile 5/6 Jerry Troyer 12:54 6 May '09   Nice work! However, if this does not compile for Windows Mobile are you planning to make a version available? Sign In·View Thread·PermaLink 2.00/5 (1 vote) Re: Does this compile for Windows Mobile 5/6 Tim Deveaux 12:00 7 May '09   No plans that I know of (in my status as adjunct toolbox mechanic and chief workie's helper). Not sure a port of the whole toolbox would be appropriate, though, as it's a bit of a mixed bag - if there are some controls you and/or others would like update to target Windows Mobile, that would certainly be welcome. The Ultimate Grid might be a better candidate for a port - years ago there was a version for Win CE (no longer available though). Guess I'm just making conversation here - is there a particular control/feature your interested in? Tim Sign In·View Thread·PermaLink coxtreectrl possible feature Laan82 23:50 30 Apr '09   Hi all, First of all thank to all the ultimate toolbox team for the great work they have done with the ultimate toolbox and the ultimate grid. Then come to my question I have a problem with a gui that I have to do. I need a control that has multicolumn tree structure. So I look to coxtreectrl but my problem is that I need to insert in the column not only text or simple combobox but instead of it I have to insert progress bar. Is it possible to do this? Thank you in advance for the help Sign In·View Thread·PermaLink Re: coxtreectrl possible feature Tim Deveaux 14:36 3 May '09   One option is to use the Ultimate Grid with the expand celltype (see the GroupingGrid demo) then take advantage of the existing progress bar celltypes. The expand celltype needs a bit of work to act like a full blown tree control, but if the level of nesting needed is not great it might be passable. The alternative, I guess, would be to derive a class from COXTreeCtrl and override DrawItem. Tim Sign In·View Thread·PermaLink Re: coxtreectrl possible feature Laan82 6:35 13 May '09   Hi Tim thank for your answer! I have looked on GroupingGrid demo my question now is: it is possible to add at the row in witch the expansion control is present another control? So for example i can create two column instead of one in that row so I can make another control in the second column? Sign In·View Thread·PermaLink

Last Visit: 15:32 8 Nov '09     Last Update: 15:32 8 Nov '09 1234567891011 Next »