This new release is smaller than usual but does contain a new Toolkit control called the KryptonTrackBar. It acts like the standard windows version allowing the user to drag a position indicator along a track. It also has the ability to draw the track as a triangle and so giving the appearance of a volume control. Always provided are a number of bug fixes and more minor additions.
Please download using the following direct link…
The latest maintenance release of the Krypton Suite is now available for download.
Please download using the following direct link…
Major Change
– Moved all design time classes to separate assembly
New KryptonDataGridView Columns
– KryptonDataGridViewComboBoxColumn
– KryptonDataGridViewNumericUpDownColumn
– KryptonDataGridViewDomainUpDownColumn
– KryptonDataGridViewMaskedTextBoxColumn
– KryptonDataGridViewDateTimePickerColumn
Major Bug fixes
– TAB key works inside Navigator
– AutoComplete works for KryptonComboBox
– KryptonGallery memory usage improved
A beta version of the next release is now available for testing. It is number 4.1.4 and contains bug fixes and some minor new functionality with the addition of some KryptonDataGridView columns. You can download using the following link…
One of the new features of .NET Framework 4.0 is the introduction of Client Profiles. The Client Profile is a cut down version of the full .NET Framework that only includes the essential assemblies needed for client based applications. The idea is to reduce the download/install size for this common deployment scenario. Design time classes are not part of the client profile because they are implicitly only needed for designing and not for running your applications.
At the moment Krypton cannot be used in this situation because the Krypton design time classes are placed inside the same assembly as the relevant controls. So the Krypton Toolkit design time classes are inside the Toolkit assembly, Krypton Ribbon design time classes inside the Ribbon assembly and so forth. But the design time assembly is not included in the client profile and so the Krypton assemblies will not be loadable.
To enable this scenario I have now created a new ComponentFactory.Krypton.Design assembly and moved all the design time classes into it. This means you can write a client profile application that references the Krypton Toolkit/Ribbon/Navigator/Workspace/Docking assemblies and it will work just fine because the Krypton assemblies no longer reference the System.Design namespace.
Note that client profiles are a feature exposed in Visual Studio 2010 and so you will only be aware of them if you have downloaded and played with that version.
The KryptonPage has two new flags…
These are used in conjunction with the Navigator flags of the same name to decide if the page can be dragged out of the navigator control or reordered. This provides per-page control over the actions rather than having the same restriction applied to all pages.
A new Navigator event called BeforePageReorder is also added that allows you to cancel the movement of a page during reordering actions. This allows the following common scenario to be implemented.
If you have a page that you want to remain always at the start of the set of pages then you can set the AllowPageReorder flag to False for that page. This prevents the user from being able to reorder that individual page. Then you can intercept the BeforePageReorder event and Cancel the event any time a page wants to be moved before our first page. Now you have a setup where all but the first page can be reordered but none of the pages can be moved before the first one. You could also implement more complex requirements such as always keeping a particular page after another in the list of pages. Although anything that complex is likely to confuse the user.
Note that these new flags and event only relate to user dragging actions. You can still add a page anywhere you like programmatically.
