Error when using QFileDialog::getOpenFileNames

Please_Help_me_D

Hi,

I try to implement file dialogue in a way to allow picking multiple files. So as in the example from the documentation I use the code:

    QStringList segyFiles = QFileDialog::getOpenFileNames(
                            this,
                            "Select one or more SEGY files to open",
                            "/home",
                            "SEGY (*.seg *.sgy *.segy)");

And in debug mode I get an error:
: -1: warning: an error occurred in the debugger: Exception at 0x7ffb06daa839, code: 0x6ba: RPC server unavailable, flags = 0x1 (execution cannot be continued) (first chance)

I use Windows 10, Qt 5.14.1, MSVC 2017 x64

JonB

@Please_Help_me_D
I think you will find this is an ignorable error/warning message, hence only seen in debug mode. These types of messages do crop up, not just from Qt. At a guess, behind the scenes the dialog is considering whether it can get at the network. This is probably harmless/intended error, but from debugger you sometimes see things like first-chance exceptions reported which you wouldn't see normally and can ignore.

Also

On Windows, and macOS, this static function will use the native file dialog and not a QFileDialog.

If that's you, the exception may be occurring in native-dialog code.

Please_Help_me_D

By the way, this error occurs only in debug mode

JonB

@Please_Help_me_D
I think you will find this is an ignorable error/warning message, hence only seen in debug mode. These types of messages do crop up, not just from Qt. At a guess, behind the scenes the dialog is considering whether it can get at the network. This is probably harmless/intended error, but from debugger you sometimes see things like first-chance exceptions reported which you wouldn't see normally and can ignore.

Also

On Windows, and macOS, this static function will use the native file dialog and not a QFileDialog.

If that's you, the exception may be occurring in native-dialog code.

Please_Help_me_D

@JonB Thank you!
I will just ignore it. Probably this is just Windows and macOS thing as you cited from documentation