HandyOrg / HandyOrg/HandyControl
[Feature request] Make `PropertyGrid.PropertyResolver` settable
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
See #1285 for more details. Raising here to allow separate tracking.
Allow the PropertyGrid.PropertyResolver to be changed to support using a custom resolver.
Describe the solution you'd like
Allowing the PropertyGrid.PropertyResolver to be changed allows an App developer to implement custom editors and add automatic support for them to the PropertyGrid, rather than requiring the models to specify the property editor via the EditorAttribute.
Describe alternatives you've considered
You can current extend the PropertyGrid control and override the PropertyResolver property. However, extending controls is significantly more work, requiring the duplication of styles etc. You can also use the EditorAttribute, however, this is not always possible when you don't control the models.
Additional context
N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the PropertyGrid control and inspect the PropertyResolver property, then read issue #1285 for the related context. Done means an app developer can change the resolver and use a custom resolver for automatic editor support without extending PropertyGrid or relying on EditorAttribute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100