CheckBoxCellType displayed blank after Windows theme change / RDP reconnect

Posted by: lee.hs on 16 October 2026, 1:16 am EST

  • Posted 16 October 2026, 1:16 am EST - Updated 16 October 2026, 1:29 am EST

    Hello MESCIUS Support Team,

    We`ve reproduced this issue by turning on the Windows Contrast Theme while a Farpoint Spread module is running. (System → Accesibility → Contrast Theme)

    We are using Spread for WinForms in our application and would like to ask about the issue described below.

    [Environment]

    • Product: Spread for Windows Forms
    • Assembly version: FarPoint.Win.Spread 4.0.3512.2008 / 14.45.20213.0
    • .NET Framework: [4.x]
    • OS: Windows 10 / Windows 11
    • FpSpread settings: VisualStyles = Auto (default), DefaultSkin = DefaultSpreadSkins.Office2007
    • Cell type: a class derived from FarPoint.Win.Spread.CellType.CheckBoxCellType (it only overrides IsReservedLocation; no custom painting)

    [What we have tested]

    • Moving the mouse cursor over the blank checkbox cells: not recovered.
    • Calling Invalidate(true) / Refresh() on the FpSpread after WM_THEMECHANGED: not recovered.
    • Toggling VisualStyles (Off → Auto) after the theme change: not recovered.
    • Re-assigning the CellType of the checkbox columns: not recovered.
    • Setting VisualStyles = Off after the theme change: recovered (drawn in classic style).
    • Restarting the application: recovered.

    From these results, it seems that the theme data used for drawing checkboxes (e.g. in FpVisualStyleRenderer) is cached and not refreshed after a theme / session change. Please correct us if this is not the case.

    [Questions]

    1. Is this a known issue in Spread for WinForms?
    2. Is there a hotfix or a later build of that versions that fixes it?
    3. Has this been fixed in a later major version (v15 or later)? If so, in which version?
  • Posted 16 October 2026, 7:49 am EST

    Hi,

    We tested the behavior you described by following the same steps and were able to reproduce the issue in both the v14.1 and v14.2 releases. However, the issue appears to be resolved in v15, as we were unable to reproduce it using the same sample project.

    Therefore, if you already have a license for Spread .NET v15, we recommend upgrading directly to that version to resolve the issue.

    Best Regards,

    Kartik

  • Posted 19 October 2026, 3:04 am EST

    Hi,

    Unfortunately, We don`t have any license for Spread .NET v15.

    We need a patch for 4.0.3512.2008 / 14.45.20213.0.

    Best Regards,

    Lee

  • Posted 19 October 2026, 7:53 am EST

    Hi Lee,

    Please note that all bug fixes and new features are included in the latest releases, and we do not provide patches for older versions. Furthermore, Spread .NET v14 is a legacy version that is no longer supported, so a fix will not be provided for this version.

    During further testing, however, we found that the issue could also be reproduced in the latest release. We are therefore consulting with the development team to get their insights and will let you know of any updates as soon as possible.

    [Internal Tracking ID: SPNET-56308]

    Best Regards,

    Kartik

  • Posted 21 October 2026, 11:55 pm EST

    Hi Lee,

    Thank you for your patience while we discussed this issue with the development team.

    The team has confirmed that this is a bug in Spread.NET. The issue has been fixed internally, and the fix will be included in the upcoming v20 release.

    Best Regards,

    Kartik

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels