As the last addition for the new KryptonTrackBar it has now been made available as a group element inside the KryptonRibbon tabs. By default it does not draw the background as you will most likely want the ribbon background to show through. It works in vertical or horizontal orientation and by modifying the TrackBarSize between Small, Medium and Large options you can get the appearance to look appropriate for your ribbon group.

The KryptonTrackBar is now completed. 

It has a TrackBarSize enumeration property with three values of Small, Medium and Large. You can see the difference in sizing in the above image that shows them in size order. It has all the same properties as the standard windows control and so you can specify the tick marks to be below, above, both or none as needed. Above you can see the first three of those options displayed.

Altering the Orientation to vertical gives the following…

The above is drawn for the Professional System palette under Windows 7. The first image was using the Office 2010 Blue palette.

In the following image there is a standard windows TrackBar and two KryptonTrackBar instances. Can you spot which is which?

As you can tell the control is not quite finished as yet. The control is fully working allowing you to use the mouse to move the marker, use the keyboard and even responds to the mouse wheel. Now I just need to hook it into the rendering engine and add some code to actually draw appropriately.

With great relief I managed to work out the problem and as luck would have it I solved the problem just 10 minutes before Microsoft support called me to investigate the bug report. Thanks to Lex Li for pointing me at the support website instead of the connect site for reporting the issue.

So what was the problem? I already had VS2008 installed and had setup the symbol server settings so I could step into and see the source code for the framework Windows Forms code. This has been very handy in the past for tracking down problems by allowing me to see exactly what was happening in the base classes. Reflector is an excellent tool but there is nothing quite like stepping through the real code.

Well it seems that VS2010 was using the already defined settings and this was the cause of the issue. I removed the symbol server settings and it all working perfectly. Put them back again and it takes essentially forever to try and start-up debugging an application. It never occurred to me until I checked that VS2010 would automatically be using the same settings as defined in VS2008. I just assumed you had to set them up manually for each Visual Studio version.

A quick update on the VS2010 problem. As recommend by commenter’s I have added a bug report on the Microsoft Connect site. If you want to vote the bug upwards it might have a greater chance of being investigated… (hint hint)…

Microsoft Connect - Bug Report

In the meantime I have restored a system image that I prudently took immediately before the install and so I’m back again working away although only with VS2008 at the moment. Even-money says the fix from Microsoft will be to wipe the machine and install everything from scratch. Not something I am looking forward to doing as it takes a couple of days to get everything up and running to the point of being able to build Krypton automatically again.