DataGridTextBox's default property points to a non-existing property
See original GitHub issueIn the following line:
The [DefaultProperty]
tag points to the property GridEditName
which doesn’t exist. I’m not sure which property this was really meant to point to - especially considering this class doesn’t have any properties.
Discovered as part of PR #86
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Detect blank cell fill with default value on enter/leave ...
From my datagrid data template textbox value filled from a file, i want to restrict the end user to enter integer with 'dot'...
Read more >Data Grid - KX Dashboards
If at least one column has a Footer property set to a value other than None , the footer section appears as the...
Read more >Set the default value of a Datagriddropdown using Textbox
Hi How do I set the default value of a Datagrid dropdown ... You need to set the Value property of both components...
Read more >DataGridTextBox Class (System.Windows.Forms)
Initializes a new instance of the DataGridTextBox class. Properties. AcceptsReturn. Gets or sets a value indicating whether pressing ENTER in a multiline ...
Read more >DataGrid.EditItemIndex Property (System.Web.UI. ...
The index of an item in the DataGrid control to edit. The default value is -1, which indicates that no item in the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Base on my experience from CoreFX repo, it is best to update milestones on closed issues and PRs on regular basis, after the fact. I do it every 1-4 weeks on CoreFX, at minimum prior to a release. There is no way all engineers will pay attention to milestones. It is lost battle + it is easier to do batch changes later on than train everyone and push process on them 😉 (I am big believer in minimal process).
BTW: Some repo don’t care about milestones on closed issues at all … it is repo maintainers preference (I see the value for community, etc., but sadly it is not something I can easily convince everyone else to agree with - I tried and failed, so I keep just recommending it and highlighting the value long-term).
That said, I will fix this one 😉
@dotMorten assigning to you as you volunteered 😉