In R2 2018 Release we released the standalone usage of ExplorerControl and the CurrentDirectoryPath works only as a setter. When user sets it- it navigates to the directory with the given path. It would be useful for the clients to have this property with working getter - to provide the path of the current folder.

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.

For example user might need to show files in FolderDialog or filter the folders somehow in all dialogs.

Currently this could be achieved with custom style for OpenFolderDialogControl, binding the ListBox to CurrentParentDirectory.Children and use converter. By default this binding is to CurrentFileSystemObjects.

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

Check the attached images for better clarification.

OpenFolderDialog with no FileName specified. Select Drive C and the press Open Folder - Exception in PreserveLastAccessDirectoryIfNeeded method.

Add a full autocomplete support - while the control is focused, type certain keys and the file dialogs should select the relative match for the currently typed text.

If you open a folder, but you doesn't select a child folder from the list shown in the explorer, when you click on the Open button the FileName property is empty.

To work this around you can create a custom RadOpenFolderDialog and override its GetViewModel. Then expose a public property with the view model. And when you close the dialog, check the IsDirectirySelected property of the view model. If so, return the Path property of the view model. Otherwise, use the standard approach and get the folder via the dialog's FileName property. 

public class CustomOpenFolderDialog : RadOpenFolderDialog
{
    public OpenFolderDialogViewModel ViewModel { get; internal set; }

    protected override OpenFolderDialogViewModel GetViewModel()
    {
        this.ViewModel = base.GetViewModel();            
        return this.ViewModel;
    }
}

---------------------------------

CustomOpenFolderDialog openFolderDialog = new CustomOpenFolderDialog();
openFolderDialog.Owner = this;
openFolderDialog.ShowDialog();
if (openFolderDialog.DialogResult == true)
{
     string folderName = String.Empty;
     if (!openFolderDialog.ViewModel.IsDirectorySelected)
     {
        folderName = openFolderDialog.ViewModel.Path;
     }
     else
     {
         folderName = openFolderDialog.FileName;
     }                
}

Currently mobile phones are not visible in the navigation tree of the file dialogs.

Make them available like in MS Explorer and file dialogs.

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.

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.

Open/Save File/Folder dialog with implicit styles.

Change a theme dynamically by merging resource dictionary containing the styles for Office2016/ Office2016Touch / Fluent Theme.

Show the dialog and open the details grid (view). XamlParseException occurs - cannot find the resource "GridViewValidationToolTipTemplate"

Click on Drive / Folder in the Navigation tree should put its Name in the AutoComplete box and then pressing the Open Button of the dialog should choose the selected drive / folder and close the dialog.

A binding error is thrown in RadOpenFolderDialog when it is shown.

 System.Windows.Data Error: 40 : BindingExpression path error: 'IsSearchActive' property not found on 'object' ''OpenFolderDialogViewModel' (HashCode=65514185)'. BindingExpression:Path=IsSearchActive; DataItem='OpenFolderDialogViewModel' (HashCode=65514185); target element is 'FileDialogSearchPane' (Name=''); target property is 'IsSearchViewActive' (type 'Boolean')

If extension filter contains *.TXT but the file is named File1.txt, it is filtered in the main pane of the File/FolderDialogs. It shouldn't be filtered, jut like it is in MS Win 32 File dialogs.

Overwriting file with extension not registered in the file system but present in the Extensions Filter ComboBox might result in duplication of the extension in the resulting FileName.

For example you have empty.stp file on your desktop.

Choose the file with SaveFileDialog , chose the STP file extenion in the Filter combo box.

Press Save.

The resulting FileName of the dialog will be empty.stp.stp but it should be empty.stp.

Available in LIB Version 2017.3.1225.

SaveFileDialog does not open overwrite confirmation message box if the file name is typed with the default extension at the end.

For example, you have "empty.txt" file on the desktop. You open SaveFileDialog, type empty, select TXT extension on the filters list on the bottom. Remove the .txt from the file name (if it is there) and press Save. 

Expected: Confirmation window for overwriting the file should be opened.

Actual: No confirmation window opens.

Add localization support for RadFileDialogs.