New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve all dialogs of choosing files #139
Comments
Not related to bug report, but you may be interested... In Debian and distros based on it WINE in currently packaged by this way:
|
Installed packages:
|
Fixup dialog's initial value 783634d |
jfyi: #140 |
It does not work as expected. When user see current path as |
Also in "Wine Version Manager" dialog nothing have been changed at all: each time open file dialog opens in user home directory. |
hi @tehnick yea, I missed Version Manager for some reason. is the the first report about '/usr/lib/wine/wine64' related to 'Wine Version Manager' too? |
This is just a sample. I was lazy to invent a new one... |
Hmm, probably I have made conclusion too quickly. I have just re-checked and in other places file choosing dialogs work fine. And as for opening of empty path it looks like this is a Qt feature: open file dialog will be opened in last path which was used previously during current session of work with a program. |
One thing that everybody would like is an option to choose folders, and auto-add wines from this folders, for example, let's suppose I added the folder "~/.local/share/lutris/runners/wine", so every time Q4wine detects a folder inside this one, it will verify if it is a wine folder, and add it automatically. |
When you call
QFileDialog::getOpenFileName()
the current value fromQLineEdit
should be used if it is not empty (but even if it is empty Qt library will resolve this situation in a proper way).Currently usage (of some) of these dialogs is not convenient. For example:

If you click on choosing file button
QFileDialog::getOpenFileName()
will be open with a path into home directory instead of path to/usr/lib/wine/wine64
...The text was updated successfully, but these errors were encountered: