Using RadOpenFileDialog reports a lot of binding errors. #26 seems to happen all the time, whereas #40 is related to the length of the initial directory.
The dialog is working, but those errors are really disturbing. The more false binding errors we get, the higher the possibility is that we miss real errors. Suppressing them by setting the error level to Critical is not a solution, as it will suppress real errors as well.
System.Windows.Data Error: 26 : ItemTemplate and ItemTemplateSelector are ignored for items already of the ItemsControl's container type; Type='RadWatermarkTextBox'
System.Windows.Data Warning: 40 : BindingExpression path error: 'IsHidden' property not found on 'object' ''OpenFileDialogViewModel' (HashCode=39129256)'. BindingExpression:Path=IsHidden; DataItem='OpenFileDialogViewModel' (HashCode=39129256); target element is 'RadBreadcrumbBarItem' (Name=''); target property is 'Visibility' (type 'Visibility')
System.Windows.Data Warning: 40 : BindingExpression path error: 'IsSystemHiddenActual' property not found on 'object' ''OpenFileDialogViewModel' (HashCode=39129256)'. BindingExpression:Path=IsSystemHiddenActual; DataItem='OpenFileDialogViewModel' (HashCode=39129256); target element is 'RadBreadcrumbBarItem' (Name=''); target property is 'Visibility' (type 'Visibility')
System.Windows.Data Warning: 40 : BindingExpression path error: 'IsHidden' property not found on 'object' ''OpenFileDialogViewModel' (HashCode=39129256)'. BindingExpression:Path=IsHidden; DataItem='OpenFileDialogViewModel' (HashCode=39129256); target element is 'RadBreadcrumbBarItem' (Name=''); target property is 'Visibility' (type 'Visibility')
System.Windows.Data Warning: 40 : BindingExpression path error: 'IsSystemHiddenActual' property not found on 'object' ''OpenFileDialogViewModel' (HashCode=39129256)'. BindingExpression:Path=IsSystemHiddenActual; DataItem='OpenFileDialogViewModel' (HashCode=39129256); target element is 'RadBreadcrumbBarItem' (Name=''); target property is 'Visibility' (type 'Visibility')
System.Windows.Data Error: 26 : ItemTemplate and ItemTemplateSelector are ignored for items already of the ItemsControl's container type; Type='RadBreadcrumbBarItem'
On Windows Server 2012 R2, the Search field in the ExplorerControl doesn't appear to work. This is observable using the Demo app.
When you type into the Search box, the main pane clears of all file/folder entries, but the matching results never appear.
(Note: Windows Server 2012 R2 isn't available in the OS box, so I chose 2008.)
Expose an event that allows you to cancel the navigation to a folder. For example, if you enter an address in the breadcrumb, click the back button, or select a directory in the navigation tree, then you should be able to cancel the navigation.
This can be done via a new event that have a Cancel property in its arguments, for example.
The naming shown here is not mandatory.
It would be nice to have some additional public properties and commands for ExplorerControl. For example:
Thanks for your consideration!
Hello.
I've created buttons that are bound to FileDialogCommands for sending commands to an ExplorerControl, as shown here:
https://docs.telerik.com/devtools/wpf/controls/radfiledialogs/features/commands
Everything works when the ExplorerControl is visible. However, if the ExplorerControl's Visibility is set to Collapsed (which I need based on a condition), the Command bindings on the buttons throw the below error:
System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Windows.Controls.FileDialogs.ExplorerControl.CanExecuteHelper(Object sender)
The UserControl that hosts the ExplorerControl is being imported through MEF. I don't know if that's a factor.
Either way, it looks like a null check might be needed for the InternalViewModel property.
Can you please add the ability to select (and scroll into view) a file/folder in the RadFileDialog by keyboard? i.e. when focused within the files section of the dialog, typing 's' should scroll to the first file starting with 's' and select it.
All the Win32 and WPF file dialogs support this.