[Bug 42645] File dialog usability

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=42645

freddi34 at yahoo.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |comdlg32

--- Comment #2 from freddi34 at yahoo.de ---
Thank you very much for your reply.

I searched through the source code and identified that dlls/comdlg32/filedlg.c
and the accompanying files are related to this. 


>> - editable address
> This is only present with "newer" dialogs that we don't fully implement.
Is there ongoing work to implement these or is this something not
feasible/blocked for the foreseeable future?

>> - droppable for native paths (drag&drop a folder from a native file manager,
>> this is commonly supported in e.g. GTK)
>I can't comment on that.
The file list (shell browser) in a GTK file dialog is droppable so that you can
drag and drop a file/folder from another application and make the file dialog
navigate to this folder, where you can then select a file. This is faster then
navigating with many clicks through the file system tree. However I just
noticed this is only between GTK applications and not a more common pattern (QT
file dialogs are not droppable and Windows would move a a dropped file into the
folder that is already opened in the file dialog). 
So this suggestion is maybe not optimal.

>> - list of recently openend locations in this WINEPREFIX
> Some bits of that are implemented I think, but probably not everything needed.
Is the ShellBrowser able to display icons/filenames for a given list of files
even if these are not in a "real" directory? Then we need to find out if and
where Wine keeps track of recent files and how to push them into the
ShellBrowser. 
Some Windows file dialogs have a side panel with bookmarks etc. but I think the 
I think the least-invasive solution is to have a "Recent Files" toolbar button
next to the "Desktop" button.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.