When using PsfLauncher to start a process via shell launching (starting a native app by specifying a file with a given extension, like .txt or .pdf), the launch works great but PsfLauncher investigates the exit code of the process and will report an error via a popup dialog if not zero.
There are instances when the process returns non-zero exit codes, but it should be safe to assume that the application should have already informed the end-user of any issues if that is necessary. The launcher code should record the exit code for debugging purposes using logging.
I have a fix for this and will include in the next batch.
When using PsfLauncher to start a process via shell launching (starting a native app by specifying a file with a given extension, like .txt or .pdf), the launch works great but PsfLauncher investigates the exit code of the process and will report an error via a popup dialog if not zero.
There are instances when the process returns non-zero exit codes, but it should be safe to assume that the application should have already informed the end-user of any issues if that is necessary. The launcher code should record the exit code for debugging purposes using logging.
I have a fix for this and will include in the next batch.