Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

only one control per cell #1534

Closed
johnbo691 opened this issue Nov 12, 2022 · 1 comment · Fixed by #1850
Closed

only one control per cell #1534

johnbo691 opened this issue Nov 12, 2022 · 1 comment · Fixed by #1850
Assignees
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-framework/svc help wanted Good for community contributors to help [up-for-grabs] in-pr okr-health Content-health KR: Concerns article defects/freshness or build warnings. Pri2 Medium priority winforms/subsvc

Comments

@johnbo691
Copy link

johnbo691 commented Nov 12, 2022

Type of issue

Missing information

Description

How can an overview of the TableLayoutPanel control fail to mention that each cell can only contain one child control, and then not tell the reader how to work around that limitation? Why would that not be an obvious bit of information to include in an introduction to a control? You only mentioned this fact once, and that was near the end of the last article for TableLayoutPanel.

The TableLayoutPanel control can contain only one child control per cell.

Page URL

https://learn.microsoft.com/en-us/dotnet/desktop/winforms/controls/tablelayoutpanel-control-overview?view=netframeworkdesktop-4.8

Content source URL

https://github.com/dotnet/docs-desktop/blob/main/dotnet-desktop-guide/framework/winforms/controls/tablelayoutpanel-control-overview.md

Document Version Independent Id

3a9becfb-2213-8fd4-8003-2d7c1b14e49c

Article author

@adegeo

@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Nov 12, 2022
@adegeo adegeo added the doc-bug Problem with the content; needs to be fixed [org][type][category] label Nov 21, 2022
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Nov 21, 2022
@adegeo
Copy link
Contributor

adegeo commented Nov 21, 2022

Great point! Thank you for opening this issue. I'll add it to the backlog. If you would like to contribute, you can submit a fix by editing the original article. Click on the Content Source link at the bottom of your original comment. To learn how to edit, see the Editing files in a repository article from GitHub.

@adegeo adegeo added the help wanted Good for community contributors to help [up-for-grabs] label Nov 21, 2022
@dotnet-policy-service dotnet-policy-service bot added the okr-health Content-health KR: Concerns article defects/freshness or build warnings. label Jan 19, 2024
@adegeo adegeo self-assigned this Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-framework/svc help wanted Good for community contributors to help [up-for-grabs] in-pr okr-health Content-health KR: Concerns article defects/freshness or build warnings. Pri2 Medium priority winforms/subsvc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants