Open PDF using Button Click

[Cobra91151]

Hi! I think your file path is wrong. Try my solution:

QDesktopServices::openUrl(QUrl::fromLocalFile(qApp->applicationDirPath() + "/docs/" + "nameof.pdf"));

QDesktopServices::openUrl(QUrl::fromLocalFile(qApp->applicationDirPath() + "/docs/" + "nameof.pdf"));

To copy to clipboard, switch view to plain text mode 

[tndave]

Hi! I think your file path is wrong. Try my solution:

QDesktopServices::openUrl(QUrl::fromLocalFile(qApp->applicationDirPath() + "/docs/" + "nameof.pdf"));

QDesktopServices::openUrl(QUrl::fromLocalFile(qApp->applicationDirPath() + "/docs/" + "nameof.pdf"));

To copy to clipboard, switch view to plain text mode 

Cobra91151

that worked like a charm! Thank you very much for your assistance. Gonna save this info for future use lol.

[d_stranz]

Defensive programming tip: Always create a local QString variable to hold the result of expressions like

qApp->applicationDirPath() + "/docs/" + "nameof.pdf"

qApp->applicationDirPath() + "/docs/" + "nameof.pdf"

To copy to clipboard, switch view to plain text mode 

so that when things don't work as expected, you can look at the contents of the QString in the debugger or a QMessageBox in release mode and verify that the string actually contains the path you expect.

The environment that gets set up when you run in the debugger vs. running standalone from the command line (or an icon click from the desktop) often leads to unexpected values for paths. If you simply build a string and pass it directly into a method, you don't really have any good way of examining that string to figure out what's wrong.

[tndave]

Defensive programming tip: Always create a local QString variable to hold the result of expressions like

qApp->applicationDirPath() + "/docs/" + "nameof.pdf"

qApp->applicationDirPath() + "/docs/" + "nameof.pdf"

To copy to clipboard, switch view to plain text mode 

so that when things don't work as expected, you can look at the contents of the QString in the debugger or a QMessageBox in release mode and verify that the string actually contains the path you expect.

The environment that gets set up when you run in the debugger vs. running standalone from the command line (or an icon click from the desktop) often leads to unexpected values for paths. If you simply build a string and pass it directly into a method, you don't really have any good way of examining that string to figure out what's wrong.

Thank you very much for the tip d_stranz. Being somewhat new to C++ and QT any and all tips are welcome