Here you can see the drawing of check boxes and how the highlight for the selected/tracking node is immediately adjacent to the check box itself. This is not very pretty and I would prefer a pixel gap between the check box and the highlighting but this is not possible because that is the method expected by the tree control.

You can assign an ImageList to the KryptonTreeControl and then use the per-node image index to draw images by the nodes. Luckily the standard tree does have a gap between the right of the image and the node highlighting so the appearance looks tidier than for check boxes.

Also implemented is the use of the StateImageList that is used to provide an optional per-node image at the left of the node drawing. In this example I used set this up on the top two nodes only.

I honour the BackColor, ForeColor and NodeFont overrides that are defined per-node. This allows you to provide a custom look for each node to reflect status.

To make like a little easier for developers I have added a new class called KryptonTreeNode that derives from the standard TreeNode class. It adds an extra property called LongText that is an extra string that will be drawn when defined to the right of the standard node text. It also includes a LongForeColor and LongNodeFont pair of overrides allowing the l0ng text to be drawn differently.

Note that apart from the KryptonTreeNode there is no new functionality in the control. It is really just a standard TreeView with some custom drawing and so any requests for new features will not be possible. It is just a TreeView!

So far I have implemented drawing the node text and the tree plus/minus nodes and lines. You can see two examples below, the first using the Office 2010 Blue palette and the second the professional palette.

The biggest change is the inclusion of help for Visual Studio 2010 SP1. Note that you do need the SP1 for Visual Studio 2010 in order to see the help. If you have not already installed it then you should do so before upgrading Krypton.

Font measuring has been fixed for the Input/Message/Task dialog boxes. The Validating and Validated events are now fired for the input controls. There are four new label styles that speed up development as well as numerous crash fixes. Check out the Toolkit and Ribbon change list documents using the links below to see a full list of changes.

Download 4.3.2

Toolkit Change List
Ribbon Change List

I spent a couple of different attempts investigating this with no luck. No matter what I did and how I looked at the scenario the Krypton code did not seem to be doing anything wrong. Fortunately someone spotted a Microsoft Knowledge Base article describing this issue and presenting a workaround. You can read it here.

The solution to the above problem was to add the following new control and then replace the 4th instance of the KryptonNavigator with the new KryptonNavigatorDelay class.

 public class KryptonNavigatorDelay : KryptonNavigator
 {
   protected override void OnSizeChanged(EventArgs e)
   {
     if (Handle != null)
       BeginInvoke((MethodInvoker)delegate
          { base.OnSizeChanged(e); });
   }
 }

This results in the following appearance when resizing the window at runtime.

The issue is with the operating system and seems to manifest itself under Windows 7 64bit when you have a depth of around 16 deep. Testing with various different controlsdoes not seem to make much difference in the depth required to see problems. Apparently the same problem can occur under 32bit operating systems but not until you have a much deeper level of nesting. Hence you are only likely to have encountered this problem under 64bit.

I cannot simply at the above code to every Krypton container because the solution causes a delay when drawing the control as the BeginInvoke delays execution of the delegate until the current windows message has been completed. So if you experience the issue then you need to check your nesting depth and look at implementing the work around at an appropriate level in the control hierarchy.

Visual Studio 2010 SP1
Note however that you need to have SP1 for Visual Studio 2010 as the SP1 includes an update to the Microsoft Helper Viewer that includes a standalone browser as shown above. This should not be a major issue as developers should be using the latest version anyway.

Installer Size
Another downside is that the installer has ballooned because it includes the extra help so now it is ~116MB instead of the ~67MB before. Given that a large chunk of the older size was the help build used for Visual Studio 2005/2008 and you can see that something like 90% of the total installer size is actually just help.

HelpStudio Tips
For those that are also using the HelpStudio product I can pass along a couple of tips. The output from the HelpStudio build is a .mshc file that contains all the help pages.

What is not obvious is that the .mshc file will not work directly if you want to perform a silent install. We don’t want to require the user to start the help manager and start browsing for the .mshc file so it can be installed into the help system. So instead we want to run a silent install at the end of the Krypton installer.

So you need to take the .mshc file and turn it into a cab file by using the makecab utility. Then you need to sign the cab file using the signtool utility. Pass this signed cab into the silent install and then your good to go.

Another gotcha is the Microsoft Help Viewer will not add a top level node for your help collection, which is what the older help system did, and so your table of contents in HelpStudio should have a single top level node and then everything else appears as a child of that.

Of particular interest are crashes that have been fixed so that the Krypton components work under 64bit operating systems. Return values from some platform invoke calls were assumed to be 32bit when they were in fact 64bit. Check out the Toolkit change list document using the link below to see a full list of changes.

Download 4.3.1

Toolkit Change List

The switch to using the KryptonMessageBox is very easy because you only need to perform a Find/Replace of the phrase MessageBox.Show with KryptonMessageBox.Show. This is because the exact same static Show methods have been used in the Krypton implementation as exist for the MessageBox which ensures an easy upgrade path. Check out the three new samples that can be accessed from the KryptonExplorer in order to see them working and experiment with the different settings that are possible.

Also present in this release is an important bug fix. Under Windows 7 the showing of a dialog that is derived from KryptonForm can fail. The bug is very nasty in that the dialog simply fails to be drawn on the screen, which is likely to be very confusing for your users. This has now been fixed. For a full list of changes you should check out the change lists that are installed.

New Components
- KryptonMessageBox
- KryptonTaskDialog
- KryptonInputBox

Download 4.3

You can use it in the following way…

   string result = KryptonInputBox.Show("Prompt",
                                        "Window Title",
                                        "Response");

This results in the following appearance…

Don’t say I never do anything for the VB.NET community!

I would however point out that our Krypton version is not intended as an exact copy. It is very similar but it might not contain absolutely everything that is possible with the operating system version of the dialog. However, something is better than nothing and so here is what we have.

Basic Settings
The most basic settings allow for a window title, main instructions, content details, associated icon and the specification of dialog buttons.  You can omit any of these values in which case they will not be displayed. Here is an example of the dialog when they have all been specified with simple values…

CheckBox Settings
You can optionally define a CheckBox that is presented in the same area as the dialog buttons. You can define the text for the control as well as the initial checked state. This is more useful than it might first appear. A common scenario is to present warning messages to the user, but ff the user finds these annoying the checkbox could be checked to indicate that the warnings should be suppressed in the future. Or maybe the checkbox is used to indicate that the selected option should always be used in the future without the need to ask again.

Footer Settings
Additional information can be shown to the user in the footer area of the dialog. You can set an image, footer text and hyperlink text for this area or any combination of the three values. This is very useful if you want to allow additional help documentation or webpages to be shown in response to a hyperlink being pressed.

Radio Button
Use the radio button feature to present a multiple choice to the user. A simple collection property is used to specify the list of possible options and the selected value is available as a property on the KryptonTaskDialog class when the dialog has been removed.

Command Settings
This is similar to the radio buttons except the choices are presented as a set of buttons. Each button is assigned a DialogResult value and so on return from the dialog being dismissed you can check the return DialogResult to see which command was selected by the user.

As an extreme example you could even specify all the possible features and show the following…

…although I am not sure your users would appreciate such a monstrosity!

Here you have some examples of the appearance using different palettes…

The text used in the buttons is localizable and exposed via the KryptonManager component. So if you need to define text for non-English systems you can update the new GlobalStrings property of the manager and all message boxes will then use those updated strings.

For those now aware, the DWM is responsible for the Aero theme (sometimes known as the glass). Needless to say, your customers are going to be confused if a window is just plain missing. In fact your developers are going to be pretty confused as well.

The workaround for this is quite simple. You need to hook into the Shown event of the modal window and then add the following call to the PerformNeedPaint method:-

    private void Form1_Shown(object sender, EventArgs e)
    {
        PerformNeedPaint(true);
    }

I expect to release a maintenance release in about three weeks that will include this fix along with any other fixes and changes that accumulate between now and then.

Please download using the following direct link…

Download 4.2

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.

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.

Please download using the following direct link…

Download 4.1.5

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

Download Kryton Beta

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.

• DateTimePicker
• MaskedTextBox
• NumericUpDown
• DomainUpDown
• ComboBox

Here you can see a couple of example images…

To make life a little easier for the developer I have added a ButtonSpecClick event onto the columns that is fired whenever any button spec is clicked for any cell in that column. This event has parameters that made it easy to get hold of the column, cell and button spec instances involved in that click. Stops you needing to walk around the data structures finding your way from the button spec to the cell and then the column, which although not hard is certainly a pain to work out each time you need to do it.

Note that there are no button specs on the already defined Krypton columns  TextBox/CheckBox/Button/Link. This is because they work in a different way that makes it impractical to add them. All the new columns have an instance of an actual control that is used when editing the cell. So when you click on a numeric column it uses a KryptonNumericUpDown instance perform the drawing and editing. As the KryptonNumericUpDown already has support for button specs this makes it possible to add that capability by moving the button specs from the column collection into the control for the duration of editing. But the TextBox/CheckBox/Button/Link columns all perform drawing by using direct calls to the renderer and adding extra code to simulate the presence of buttons is not a pleasant thought.

Apart from a drop button and colour column what others are people in need of? I cannot promise to add what people request but if it sounds generally useful and not overly time consuming to add then I will certainly consider it.

I setup the first column with a mask of “(99) 9999-9999″ and the second is defined to use the system password character in order to hide the underlying text value. Using the masked text box is a great way of achieving a formatted appearance to underlying string values and also ensuring the user can only enter valid values.

All three columns are defined using our new column type but by altering the Format, CustomFormat and other column properties we can choose to only show and allowing editing of the Date part, Time part or both. It can handle null able columns as well, just remember to set the ShowCheckBox to True for a null able column so that the user can make an entry null able again after setting a DateTime value.

There is a property on the column so that you can draw them with the buttons all the time but the default is as above. Also note that you get full auto suggest and auto append functionality in the ComboBox column. You can see that in action above as well.

You can now use the KryptonComboBox in a text typed column. This is great if you have a small set of possible values and allows the full list to be available from the drop down. Also useful if you have common values that you want to be accessed from the drop down whilst the editing portion remains editable. Here you are see it in action…

Youc an specify the set of combo box strings in the columns Items collection.

A control that is less used than it should be is the DomainUpDown. It’s really handy when you want the user to able to enter any text they like but you also want them to have a simple list of common options they can scroll through. You can now use the KryptonDomainUpDown in a text typed column. Here you are see it in action…

Youc an specify the set of predefined strings in the columns Items collection.

This rather long class name can be used to add a KryptonNumericUpDown control for the editing of Decimal values in a KryptonDataGridView control. You can see the new column type in operation here…

Youc an specify the Minimum, Maximum, ThousandsSeparator, DecimalPlaces, Hexadecimal and Increment values for the column.

The single functional change is to the Office 2010 palettes. As the result of a developer poll indicated that people wanted the default size of the Office 2010 palettes changed to match that of the Office 2007 palettes. This change has been made in this release. You can however revert those palettes to the smaller size, or indeed any size you like, using the following example code…

   KryptonManager.PaletteOffice2010Blue.BaseFontSize = 8.5f;
   KryptonManager.PaletteOffice2010Silver.BaseFontSize = 8.5f;
   KryptonManager.PaletteOffice2010Black.BaseFontSize = 8.5f;

This new BaseFontSize property is available on the built-in palettes except the Professional variations. There is also a BaseFontName that allows the font to be changed away from the default Segoe UI setting.
 

Download Link
Download Krypton 4.1.1

Change Lists
Toolkit Change List
Ribbon Change List
Navigator Change List
Workspace Change List
Docking Change List

The extra functionality is a property that sets the base font size…

kryptonManager.PaletteOffice2010Blue.BaseFontSize = 9.5f;

This property is only provided on the built in palettes and can be accessed via the KryptonManager as seen in the above code example. This allows those that would like a bigger font for the Office 2010 palettes to achieve it using the above example code. Please report any issues inside the post comments or via a direct email to myself.

Download 4.1.1

This sounds like a valid issue. So I have started a poll on the forums in order to gather feedback. If a clear majority want the font made bigger to match the other palettes then the 4.1.1 release will be updated to make that happen. Note however that the ribbon fonts will not change as they look fine as they are. The ribbon is self contained and so there is no need to update the fonts for the ribbon itself.

If you want to vote then visit the forum link here…

Poll on Forums

New for Version 4.1
- Office 2010 Blue/Silver/Black Palettes
- Office 2010 Style Ribbon
- KryptonGroupBox
- Various bug fixes

Change Lists
- KryptonToolkitChangeList.doc
- KryptonNavigatorChangeList.doc
- KryptonWorkspaceChangeList.doc
- KryptonRibbonChangeList.doc
- KryptonDockingChangeList.doc

For those interested in the new Office 2010 palettes or maybe the new KryptonGroupBox control you can download the Beta of the upcoming 4.1 release from here…

Download Beta

Office 2010 Blue
Here we have the blue theme in active and inactive states…

Notice that the background of the  tabs area also changes with the window activation change. This gives a more consistent feel and makes the ribbon feel part of the window itself because its colour always matches that of the window chrome in the caption area above it. Also note the application button has been replaced with an application tab that is positioned at the start of the tabs area. New properties have been added allowing you to change the default blue colour and default File text.

On the far right of the tabs line you can see a new upwards pointing button. This is used to switch between minimized and full modes and is now present by default for all palettes. There is a new property that allows this to be turned hidden if you prefer to save the space. I think the button is a great idea as most end users are unlikely to discover that double clicking tabs with toggle the minimized mode.

If you look careful you might also have spotted that the cluster buttons no longer show with borders around them. Previously they would have a border around each button but now there is no border unless you actually move the mouse over the button. Instead each cluster has a small separator next to them so they are delineated from other group contents.

Give yourself a pat on the back if you have spotted this final change. Although not obvious the font is half a point smaller than under the Office 2007 themes and this allows more content to fit within the same space.

Office 2010 Silver/Black
Just like Office 2007 there are three themes in total and they are based on the same blue/silver and black base colours…

Aero Glass Support
Under Vista and Windows 7 the ribbon draws a little different to take advantage of the glass look and feel. Here you can see the blue scheme under Windows 7…

The window chrome has been extended downwards over the tabs area. In order to ensure the text for the tabs can still be read the background has a light gradient that extends upwards so that the darker text stands out. I have not managed to draw this exactly the same way as Office 2010 does but it is pretty close.

I’m keeping my fingers crossed that they do not make any changes between this Beta and the final release. Otherwise I will need to make additional changes. But as they have added all three schemes I expect that any changes are now going to be very minor.

Now onto the task of updating the rest of the controls with new settings.

Well now you can use the all new KryptonGroupBox control. Just like the standard windows forms control it draws a caption text over the top of a group border. Here you see an instance in the default Office 2007 Blue palette.

You can actually specify two strings plus an image for the caption.

Or move the caption to one of the other three edges.

By default the border edge is indented 50% of the height of the caption area. If you specify 100% then you get the left image below and a value of 0% gives the variation on the right.

The KryptonGroupBox is a simple little control but that does not make it any less useful in your Toolkit.

New for Version 4.0
   – VS2010 Style Docking system
   – KryptonWrapLabel
   – KryptonSeparator
   – Workspace persistence
   – Workspace max/restore feature
   – Various bug fixes

Change Lists
  – Toolkit
  – Navigator
  – Workspace
  – Ribbon

Reduced Product Line-up
Something like 90% of all sales are for the full Krypton Suite and so I intend to simplify the list of product offerings by selling only the full Suite. Existing customers with the Navigator, Workspace or Ribbon that are still within their 12 month subscription will get a free upgrade to the Suite + Source. So no customers will miss out because of the change in policy.

The Suite will also only be offered with the full source code included so the ability to buy just a license is being removed. Most companies want the source code anyway and so this reduces the number of purchase options making it a simpler decision. So the purchase page is going to have just the Krypton Suite + Source with the only options being the number of licenses you want to buy.

BARGAIN ALERT: Yes, that means you could buy the Navigator at $149 before next Wednesday and get a free upgrade to the full Suite including the source code. Reading my blog means you get the inside track and your reward is a truly once in a lifetime bargain. Or why not get a 4 pack and save even more!

New Pricing
Currently the Suite + Source is priced at $399 (USD) and the new price with the docking system added will be $499 (USD). Looking at other comparable products on the market I still think this is a reasonable price given the extra flexibility and features it offers.

New Licence Options
Last is a change to provide customers with an upper limit on costs. I hope this will tempt more of the larger outfits to consider buying the Suite for the entire development department. I am introducing Site and Enterprise license options.

A Site license will allow an unlimited number of developers within your organization but limited to one geographic location. An Enterprise license allows for an unlimited number of developers at an unlimited number of locations for your organization. Customers with 16 or more licenses at the moment will be offered the chance to convert to either the Site or Enterprise depending on their licenses requirements.

I did make a couple of other minor changes. First of all the background of the control is transparent instead of using the controls BackColor property. I also uses the palette text rendering hint so that the text has the same appearance as text everywhere else in the Krypton Toolkit. You can see the result in this image…

At the top is a KryptonWrapLabel and at the bottom a standard windows forms Label.

You can start the app but running the Krypton Explorer, selecting the Applications tab and then using the Krypton Serial Keys link. Here you can see it running on my development machine.

The bottom of the screen lists all the currently registered serial keys in the registry. To register a new key just enter it into the text box and use the register button. If it succeeds then the bottom section will update to show it.

So when a new release is made in the future you can uninstall, install the latest version and then run this app to register your new serial key. Then you should be able to load up and build your application without further actions.

NOTE: No, the serial keys in the image are not valid; they were randomly generated strings for demo purposes only!

It takes a set of custom palettes and compiles them into your assembly for ease of use. You can check it out here…

As the user moves the mouse over the control it changes the mouse cursor to indicate that it provides splitter functionality. If you press the mouse and start dragging then you see feedback drawn over the application that shows what change will occur if you release the mouse. Here you can see the visual feedback as a drag occurs…

The KryptonSeparator does not actually do anything when you release the mouse at the end of the drag as there is no way for the control to know what other controls should be resized and positioned. Instead it generates events that you can monitor and once the drag ends you use that event to decide what action to take.

This new beta has quite a few changes based on the feedback from testers of the first version earlier in the week. Most of the changes are in the date time picker and month calendar controls. Here is a full list of changes since the first beta…

KryptonDateTimePicker

• Text property now returns the actual displayed text, used to always return an empty string.
• MouseWheel now performs the key up/down action of the active text field.
• Entering 31 for the day number would not select the correct day.
• Up/Down actions on the day would not overflow within the same month.
• Mouse down on non-day parts of calendar would dismiss the context menu.

KryptonMonthCalendar

• Drawing was corrupted for many non-English culture settings.
• Can now set the background to transparent so parent background shows through.
• Changing the DayStyle could crash when using a KryptonPalette.
• When number of rows and columns were different mouse selection could crash.
• Can now enter 1 or 2 digits for the descriptive month field to change the value.

Other

• Palette upgrade tool now converts versions 12 and below to latest version 13.
• Switching Navigator between Outlook modes would cause a crash.
• KryptonComboBox would select text when you minimize/restore the form.

Download Beta 2

KryptonDateTimePicker
KryptonMonthCalendar
DateTimePicker for KryptonRibbon
MonthCalendar for KryptonContextMenu
Per-KryptonPage ButtonSpecs
Many bug fixes (consult change lists)

I will create a forum so that bugs and other feedback can be logged for the beta specific release.

Download Beta

Also update is the ribbon so you can display and modify dates inside the ribbon groups as shown here.

There is only one remaining task, allowing the entry of numeric values using the keyboard numbers. Up and down keys are fine but entering the number directly is a feature of the built-in control that speeds up data entry.

Here we have the control displayed with each of the four Format property settings of Long, Short, Time and Custom. The associated CustomFormat is defined as “MMMM dd ‘at’ hh:mm tt“.

Clicking the drop down button presents the new KryptonMonthCalendar control inside a KryptonContextMenu instance that allows the selection of a new date. The DropDown event is fired before the calendar is displayed and allows you to customize the context menu with additional menu items as required. This could be very handy if you need to add extra options such as predefined date selection.

As with the standard control you can show a check box that allows the user to specify that the date should be null. In fact I have added an extra property called ValueNullable that will help with annoying data binding scenarios. The Value property works like the standard control and always returns a DateTime value but ValueNullable will return DBNull when the check box is cleared and return a DateTime when the check box is set. That should making binding against database columns easier.

Use ShowUpDown to show a pair of spin buttons instead of the default drop down button. As with most Krypton controls you can use ButtonSpec definitions to add extra buttons to the control area.

Text Editing

The one feature currently missing, and my next task, is the ability to modify the text area using the keyboard. I need to take the focus and highlight the different fragments of text such as just the month, day, hours and so forth. Then allow the up/down buttons and other keyboard actions to modify the value. This requires parsing the format and working out the correct drawing of different sections. Not that hard but it requires quite a bit work to get it working smoothly.

Even if all the hacks could be make to give the correct presentation if would still be unpleasant having to hope that they continue to work for all future versions of Windows. It is much more work to start from scratch but I hope it will pay off in the long run and allow a greater level of flexibility. Adding additional functionality will be easier when you have the full source code and can do anything you want.

The next step was to update the background color to match the palette setting. This is where things start to go downhill as I discover the DateTimePicker does not actually have a BackColor property. No problem I think to myself, I just need to override the WndProc and handle the WM_ERASEBKGND message myself. Draw the background in the required color myself and we are good to go.

Well not so fast. Although my code is executed it makes no difference to the displayed background. This is odd so I do some Google research and discover this is a well known bug in the control. Apparently the WM_ERASEBKGND approach works with controls that do not have visual styles enabled but fails otherwise. So I removed the application level call to EnableVisualStyles and tried again. Yep, now it draws the background correctly using my code. In practice almost all .NET applications call EnableVisualStyles when they are started so I need a solution that does not insist this line of code is removed from apps.

There is one last possibility which is to call SetWindowTheme(Handle, “”, “”) for the control instance and so turn off visual styles just for that one individual control. This allows the rest of the application to run as it likes but ensures we get the background drawn for our KryptonDateTimePicker instance.

Unfortunately this last gasp attempt just falls short. It draws the border and drop down button of the control in the Windows Classic appearance which is exactly what I expect when visual styles are turned off. But it still stubbornly does not draw the text background using the WM_ERASEBKGND code! Close but no cigar.

Unless someone out there has a clever idea it looks like I need to scrap the work and begin again with a new approach.

…the Sparkle Blue palette…

…and finally the System palette…

I know some would prefer the gradient effect colors for selection but I feel this is more appropriate.

These two properties mimic those available in the standard MonthCalendar control and perform the same funtions. Use ShowToday to have a button placed on the bottom header that is used to change the current selection to today. ShowTodayCircle will provide a highlight around today’s date so that you can find it quickly. This image show both of these properties defined.

There is an OverrideToday property so that you can alter the way in which the today’s date entry is highlighted. So if you prefer to change the background or text color then you can easily do so.

ButtonSpecs

As with many of the Krypton controls you can specify ButtonSpec instances in order to add extra functionality to the control. In the above pictures you can see an extra button with the text ‘XYZ’ added to the bottom header. All button specs are added to the bottom header. If you need to add many additional options you should set a button spec to have a drop down context menu.

You can use three properties to describe the dates you would like to appear in bold. These are the same as those for the standard MonthCalendar and allow arbitrary dates, per-month dates and per-year dates. If you prefer to show the dates in a different way you can alter the OverrideBolded state information to achieve the required appearance.

Week Numbers

Many accounting applications needs to show the week number alongside the dates to help the user correctly select the day of interest. Just like the standard MonthCalendar you can set the ShowWeekNumbers property as needed.