Currently, showing a dialog can take 10-20 seconds when started in DEBUG mode. 

And 3-5 seconds RELEASE mode. Improve the loading time.

A little way to speed up is to set ExpandToCurrentDirectory to False.

Like in MS Win 32 OpenFileDialog - thumbnails with preview or details about the selected file.

Check the attached images for better clarification.

Show the actual image when the layout of the main pane is set to Medium, Large and Extra Large Icons.

Currently, the root of the file system is "This PC". Allow setting a custom folder as a root (for example, C:\Users\mivanov\Documents) and show only its children.

Currently dialogs provide only custom places pane. 

Add auto-populated built-in section with well-known quick access like in the MS file dialogs.

Provide a way to create custom Confirm dialog when overriding a file in SaveFileDialog.

Provide built-in support for the following combinations:

• Move to the previous folder:  Backspace or Alt+Left Arrow combination
• Move to the next folder: Alt+Right Arrow combination
• Change layout: Ctrl + Mousewheel combination

If the OneDrive folder is available, display it in the navigation tree of the ExplorerControl.

Currently, this can be done manually by adding the OneDrive directory in the CustomPlaces collection of the dialog.

Add support for respecting the Group Policy settings in order to hide the specified drives.

Add an API that allows you to access the columns of the corresponding FileBrowserGridView control (representing the Details layout) so you can add different settings. Or alternatively provide some property abstraction to propagate properties from the file dialogs API to the internal RadGridView columns API.

This might be a public  event (File/FolderSelecting) or property (IsSelectable) of the FileSystemInfoWrapper but user will need a mechanism to set it (control over the file/folder wrapper creation).

For example some files might be visible and not filtered in main pane but should be disabled for user selection.

Currently RadFileDialogs do not provide such tooltips when hovering files and folders.

Check the attached image for clarification.

Introduce a mechanism to allow executing search manually. Similar to the RadGridViewCommands.SearchByText command.

RadOpenFileDialog does not update FilterIndex

The RadOpenFileDialog has a property FilterIndex to get or set the index of the currently selected filter. Setting the index works fine. However, the property is not updated when the user selects a different filter. FilterIndex will always keep the value that was initially set. This is quite annoying, as we want that our customers find their most recently used filter index pre-selected.

The same problem exists for InitialSelectedLayout, which is never update either. .Net Framework's OpenFileDialog restores the most recently selected view automatically.

FileDialogs version is 2019.1.116.45

Add the option to display folder shortcuts in OpenFolderDialog and to dereference links.

Add shortcuts for accessing different elements on the UI - the search bar, the file name input, the buttons, etc. 

Currently, when the RadFileDialogs control is opened in a remote session, redirected drivers from the local machine will not be shown in the control. We could add an option to show the drivers from the local machine, which are chosen to be used in the remote session.

It appears that the display string is the last element of the path, but this can cause potential confusion when the paths are very different, but the last folder is identical. Take for example "C:\Users\Public\Documents" and "C:\Users\<user_name>\Documents". Each of these will be displayed as "Documents" in the final UI, even though the first is probably more recognizable as "Common Documents" or "Public Documents". The icon appears to be different for each, but that's not enough to distinguish them enough without first browsing the path.

It would be nice to create a seamless experience for our users between an application that uses the RadFileDialogs and their native Windows OS. To that end, having the RadFileDialogs use the same InitialSelectedLayout as the base OS would go a long way. Adding some way to identify the current Windows setting and to set the RadFileDialog accordingly would be a great help.