Skip to content

* Grouped Ribbon controls do expose designers, needs a closer look (V… - #4074

Open
PWagner1 wants to merge 2 commits into
alphafrom
V110-4059-code-todo-grouped-ribbon-controls-do-expose-designers-needs-a-closer-look
Open

* Grouped Ribbon controls do expose designers, needs a closer look (V…#4074
PWagner1 wants to merge 2 commits into
alphafrom
V110-4059-code-todo-grouped-ribbon-controls-do-expose-designers-needs-a-closer-look

Conversation

@PWagner1

Copy link
Copy Markdown
Contributor

…110)

Fix: Reuse base designer for ribbon ThemeComboBox (#4059)

Summary

KryptonRibbonGroupThemeComboBox no longer ships a near-duplicate of KryptonRibbonGroupComboBoxDesigner. It inherits the base ribbon combo box designer for move/delete/helpers, while theme-specific combo properties stay hidden via the existing Removed Designer overrides.

Related issues

Type of change

  • Bug fix (Resolved)
  • Feature / enhancement (Implemented)
  • Breaking change (API removal/rename, behavior change requiring migration, assembly/namespace move)
  • Documentation only

Changes

  • Krypton.Ribbon: Pointed KryptonRibbonGroupThemeComboBox at KryptonRibbonGroupComboBoxDesigner and removed the TODO that tracked this review.
  • Krypton.Ribbon: Deleted the near-duplicate KryptonRibbonGroupThemeComboBoxDesigner.cs.

Affected packages & target frameworks

  • Packages: Krypton.Ribbon
  • TFMs verified: project Debug build of Krypton.Ribbon

Validation

  • TestForm demo: RibbonTest (already hosts kryptonRibbonGroupThemeComboBox1).
  • Manual steps:
    1. Open RibbonTest in the Visual Studio designer.
    2. Select the ribbon group ThemeComboBox; use Move First/Previous/Next/Last, Delete, Visible, and Design Helpers.
    3. Confirm DefaultPalette remains available and editable; confirm Text, Items, DropDownStyle, and autocomplete properties stay hidden.
    4. Run the form and change themes via the ribbon ThemeComboBox.
  • Build: dotnet build ".\Source\Krypton Components\Krypton.Ribbon\Krypton.Ribbon 2022.csproj" -c Debug

Changelog

  • Entry added to Documents/Changelog/Changelog.md:
* Resolved [#4059](https://github.com/Krypton-Suite/Standard-Toolkit/issues/4059), Grouped Ribbon controls do expose designers, needs a closer look
   * `KryptonRibbonGroupThemeComboBox` now reuses the base ribbon combo box designer instead of a near-duplicate Theme-specific designer

Breaking changes & migration

None. KryptonRibbonGroupThemeComboBoxDesigner was internal and not part of the public API. Design-time verbs may say "ComboBox" instead of "ThemeComboBox"; behavior is unchanged.

Checklist

  • Builds for net472 and is C# 7.3 compatible where required
  • New compiler/analyzer warnings in touched code addressed
  • Documents/Changelog/Changelog.md updated
  • TestForm demo added or updated (features / observable bug fixes) — existing RibbonTest covers this
  • Documents/Development/ guide added (substantial features)
  • Screenshots/GIFs included (UI changes)
  • Breaking-change impact and TFM notes documented above

…110)

# Fix: Reuse base designer for ribbon ThemeComboBox (#4059)

## Summary

`KryptonRibbonGroupThemeComboBox` no longer ships a near-duplicate of `KryptonRibbonGroupComboBoxDesigner`. It inherits the base ribbon combo box designer for move/delete/helpers, while theme-specific combo properties stay hidden via the existing `Removed Designer` overrides.

## Related issues

- Closes #4059

## Type of change

- [x] Bug fix (`Resolved`)
- [ ] Feature / enhancement (`Implemented`)
- [ ] **Breaking change** (API removal/rename, behavior change requiring migration, assembly/namespace move)
- [ ] Documentation only

## Changes

- `Krypton.Ribbon`: Pointed `KryptonRibbonGroupThemeComboBox` at `KryptonRibbonGroupComboBoxDesigner` and removed the TODO that tracked this review.
- `Krypton.Ribbon`: Deleted the near-duplicate `KryptonRibbonGroupThemeComboBoxDesigner.cs`.

## Affected packages & target frameworks

- Packages: `Krypton.Ribbon`
- TFMs verified: project Debug build of `Krypton.Ribbon`

## Validation

- TestForm demo: `RibbonTest` (already hosts `kryptonRibbonGroupThemeComboBox1`).
- Manual steps:
  1. Open `RibbonTest` in the Visual Studio designer.
  2. Select the ribbon group ThemeComboBox; use Move First/Previous/Next/Last, Delete, Visible, and Design Helpers.
  3. Confirm `DefaultPalette` remains available and editable; confirm `Text`, `Items`, `DropDownStyle`, and autocomplete properties stay hidden.
  4. Run the form and change themes via the ribbon ThemeComboBox.
- Build: `dotnet build ".\Source\Krypton Components\Krypton.Ribbon\Krypton.Ribbon 2022.csproj" -c Debug`

## Changelog

- Entry added to `Documents/Changelog/Changelog.md`:

```markdown
* Resolved [#4059](#4059), Grouped Ribbon controls do expose designers, needs a closer look
   * `KryptonRibbonGroupThemeComboBox` now reuses the base ribbon combo box designer instead of a near-duplicate Theme-specific designer
```

## Breaking changes & migration

None. `KryptonRibbonGroupThemeComboBoxDesigner` was `internal` and not part of the public API. Design-time verbs may say "ComboBox" instead of "ThemeComboBox"; behavior is unchanged.

## Checklist

- [x] Builds for `net472` and is C# 7.3 compatible where required
- [x] New compiler/analyzer warnings in touched code addressed
- [x] `Documents/Changelog/Changelog.md` updated
- [ ] TestForm demo added or updated (features / observable bug fixes) — existing `RibbonTest` covers this
- [ ] `Documents/Development/` guide added (substantial features)
- [ ] Screenshots/GIFs included (UI changes)
- [x] Breaking-change impact and TFM notes documented above
@PWagner1 PWagner1 added this to the Version 110 milestone Jul 25, 2026
@PWagner1
PWagner1 requested a review from a team as a code owner July 25, 2026 16:51
@PWagner1 PWagner1 added area:ribbon All issues to do with the ribbon. version:110 All things to do with V110. labels Jul 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:ribbon All issues to do with the ribbon. version:110 All things to do with V110.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant