Skip to content

1.0.32 - orb delete no longer crashes the designer

Latest

Choose a tag to compare

@DwainSnickles DwainSnickles released this 15 Nov 02:52
· 7 commits to net10 since this release

Fixed: deleting an orb entry took the Windows Forms designer down.

The delete ran through the designer host with transaction.Commit() on whatever the host returned, and read
Ribbon.OrbDropDown without a check. A host that hands back no transaction - which the out-of-process
designer can do - made that a null reference thrown from the design surface's mouse handling, so the
design-tools server reported DesignToolsServerException: Object reference not set to an instance of an object and the click died.

  • The transaction is optional (transaction?.Commit() in a finally).
  • The ribbon and drop-down are captured once and null-checked; the entry is removed from its collection even
    when the host path fails, so the row always disappears.
  • A failure is written to RibbonLibDesign.log (next to the repo, or %TEMP% elsewhere) with the real
    stack, instead of escaping into the designer's message loop.
  • The design surface's click guard (RibbonAddPillGlyphBehavior.OnMouseUp) keeps any residual exception from
    killing the designer server.

Same code as 1.0.31 otherwise: two-pane orb menu, runtime drop-down layout fix, tab icons.

dotnet add package Dwain.RibbonLib --version 1.0.32