How to change Header Font Size

[LV]

Is it possible to change the font size on the column header in winforms Schedule Control? 

The layout I am working on are  ScheduleViewType.CustomWeek and ScheduleViewType.WorkWeek.

[Sreemon Premkumar Muthukrishnan]

Hi Lenin Varsamis,

Your requirement to change the font size for the column header can be achieved by setting the font size inside the DrawCellDisplayText event. Please find the code snippet below.

Code Snippet:

this.scheduleControl1.GetScheduleHost().DrawCellDisplayText += Form1_DrawCellDisplayText;

 private void Form1_DrawCellDisplayText(object sender, Syncfusion.Windows.Forms.Grid.GridDrawCellDisplayTextEventArgs e)

  {

      // Setting the size for the column header.

      if (e.Style.CellType.Equals("Header"))

      {

          e.Style.Font.Size = 12f;

      }

  }

Output:

We have prepared a sample based on your requirement. Please find it in the attachment.

Regards,
Sreemon Premkumar M.

Attachment: WinForms_ScheduleControl_NetCore_363c3fdf.zip

[LV]

Thanks for the reply. I will test it and let you know what is happening.

When I set the divisions per hour to 4 the control shows another small column just before the date header columns. What is this column and how can the header text be changed to avoid showing that annoying "B" letter?

[Sreemon Premkumar Muthukrishnan]

Hi LV,

We have been able to replicate the issue on our end. We are currently validating the reported issue and need some time to complete the validation. We will provide further updates on or before October 23, 2024.

We appreciate your patience in the meantime.

Regards
Sreemon Premkumar M.

[Sreemon Premkumar Muthukrishnan]

Hi LV,

We have checked and created a bug report for the reported issue “Column header is not rendered correctly when the DivisionPerHour is set above two”. We will include this fix in our upcoming Weekly NuGet release which is scheduled for November 19, 2024.

We will share the details regarding the feedback on tomorrow.

We appreciate your patience until then.

Regards,
Sreemon Premkumar M.

[Sreemon Premkumar Muthukrishnan]

Hi LV,

We have created a bug report for the reported issue “Time Column header is not rendered properly when the DivisionPerHour is set above 2”. We will include this fix in our upcoming Weekly NuGet release which is scheduled for November 19, 2024.

You can track the status of this report through the following feedback link,

Feedback Link: https://www.syncfusion.com/feedback/62492/time-column-header-is-not-rendered-properly-when-the-divisionperhour-is-set-above

Note: The provided feedback link is private, and you need to login to view this feedback.

We will let you know once it is released. We appreciate your patience until then.

Disclaimer: Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.

Regards,
Sreemon Premkumar M.

[Sreemon Premkumar Muthukrishnan]

Hi LV,

The weekly release has been postponed to 20th November 2024, we will let you know once it is published.

We appreciate your patience and understanding in the meantime.

Regards,
Sreemon Premkumar M.

[Sreemon Premkumar Muthukrishnan]

Hi LV,

We apologize for the inconvenience.

Unfortunately, we are unable to include the fix for the issue "Time Column header is not rendered properly when the DivisionPerHour is set above 2" in our Nuget Package released as promised today. We fixed the issue, but we require more time for testing and we are actively working on it. We will include the fix in our upcoming weekly NuGet release which is scheduled for November 26, 2024.

We appreciate your patience until then.

Regards,
Sreemon Premkumar M.

[Sreemon Premkumar Muthukrishnan]

Hi LV,

We would like to let you know that Essential Studio Weekly NuGet packages (v27.2.4) has been published in nuget.org with the fix for the issue “Time Column header is not rendered properly when the DivisionPerHour is set above 2”. Please let us know if you have any concerns in this.

Root Cause Details:

In the current implementation, when adding covered ranges, we include the DivisionPerHour value for the column index. As a result, if the DivisionPerHour is set to 2, the column header is included in the covered ranges, and no issues arise. However, when the DivisionPerHour is set to a value other than 2, the column value is not included in the CoveredRanges , leading to the appearance of an additional column. Therefore, we have now updated the value of the covered cell to 2 instead of DivisionPerHour.

Regards,
Sreemon Premkumar M.