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

Expose some Events of FolderBrowserDialog to match WindowsAPICodePack CommonOpenFileDialog #12799

Open
Aniobodo opened this issue Jan 16, 2025 · 1 comment
Assignees
Labels
api-suggestion (1) Early API idea and discussion, it is NOT ready for implementation
Milestone

Comments

@Aniobodo
Copy link

Event exposure will make it possible to customize the behavior of the dialog.
Of particular interest here are the already public events of CommonOpenFileDialog. This will make it possible to migrate from CommonOpenFileDialog to FolderBrowserDialog without any breaking-change of behavior.

A particular example is FolderChanging event, which can be cancelled to stop the user from navigation to subfolders; thereby enforcing that the user make the folder selection only from the folders displayed in the InitialDirectory.

Expose some Events of FolderBrowserDialog to match WindowsAPICodePack CommonOpenFileDialog

@elachlan elachlan added the api-suggestion (1) Early API idea and discussion, it is NOT ready for implementation label Jan 16, 2025
@Tanya-Solyanik Tanya-Solyanik added the untriaged The team needs to look at this issue in the next triage label Jan 19, 2025
@merriemcgaw merriemcgaw removed the untriaged The team needs to look at this issue in the next triage label Jan 22, 2025
@merriemcgaw merriemcgaw added this to the .NET 10.0 milestone Jan 22, 2025
@merriemcgaw
Copy link
Member

@JeremyKuhne to see if this is a good candidate for CSWin32 to help us to accomplish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-suggestion (1) Early API idea and discussion, it is NOT ready for implementation
Projects
None yet
Development

No branches or pull requests

5 participants