When using the FileManager and navigating through directories, the Breadcrumb does not show the path.
Reproduction: https://blazorrepl.telerik.com/GdOCYQki12iTAeWd34
Hello,
Nice work on the FileManager component, this will be incredibly useful. I would like to use this control in an Open File Dialog and the only thing I'm missing to support that is what is the selected item in the listview. If I could bind that selection then I could enable/disable my Ok button and provide the selected item(s) when the user hit's ok. Is there a way to access this information?
Thanks,
-Andy
Would like to be able to change / recall State of expanded / collapsed items in FileManager, similar to how we can with the Grid component using Groups.
On refreshing data from the database, the entire File Manager reverts to all items collapsed, which will be annoying for end users.
State management could also deal with the default view (Details vs Icons) as requested elsewhere for this component.
For true load on demand, the OnRead event should be triggered for:
- PathChanged;
- TreeView expand;
- as many more data-related actions as possible;
Sorry to bother you, but we found a problem when using the FileManager control. When you are in a directory hierarchy Home > Dir1 > DirA > DirX > DirY and you want to navigate to the parent directory say DirX using the breadcrumb, clicking on DirX, FileManager sends you to the root directory. I hope you can help me.
If there are a lot of child folders, the Breadcrumb navigation does not work correctly. The current directory does not respond to the selected one.
The FileManager is not showing icons for video files, e.g. mp4. The icon's CSS class is k-i-video, but it may need to be k-i-file-video.
The workaround is to apply the k-i-file-video icon to k-i-video:
CSS
.k-i-video::before {
content: "\e93b";
}
When the FileManager is placed in a Window/Dialog, the ContextMenu does not open.
---
ADMIN EDIT
---
Essentially, the ContextMenu is rendered but appears behind the Window/Dialog and thus it is not visible. The issue is z-index related and a possible workaround is to increase the z-index of the ContextMenu to ensure it will be visible.