Closed crumblingstatue closed 5 months ago
1: Are the quick access sections not suitable for this? \ You can add your own sections via the backend:
file_dialog = FileDialog::default()
.add_quick_access("Hexerator", |s| {
s.add_path("Some path 1", "./path-1");
s.add_path("Some path 2", "./path-2");
})
And you can access the config with file_dialog.config_mut()
.
And you can access the config with
file_dialog.config_mut()
.
Ah, good catch. I think I used to need that because the storage and config were two different structs, and I was getting overlapping borrows by borrowing the config through config_mut(&mut self)
, and also trying to access the storage.
But now the storage is in the config, so it's fine that config_mut()
borrows self.
I'll cross that one off the list.
The shortcut key is now implemented.
Let me know if you have any other ideas!
My egui project, Hexerator has switched from rfd to egui-file-dialog, but right now it's using a fork with custom patches to accommodate Hexerator's needs. The eventual goal is to not have a fork, and just depend on upstream egui-file-dialog directly. This is a wishlist of features that currently a fork is required for.
MakeFileDialogConfig
andDirectoryEntry
public. This way, the pinned folders can be read and written to by the application.~
key to work to access the home directory quickly. Maybe this should have a different default on windows, although I don't see an obvious choice for what it should be on windows, so maybe it's fine for it to be~
there as well. Downstream patch: Add home_edit_path key binding