Environment: PDFsam 5.x on Windows-11 (but also happened with PDFsam 4.x and with Windows-10).
With Windows, a general workflow is that if there is a data file of a particular type (typically, file extension), then simply double-clicking that data file will open the application, and also that data file will then be the input and default output for that application. (There are variants, such as mouse-hold and select "open with" but the same semantics of "use this [data] file as data input" still holds true.)
This doesn't seem to be the case with PDFsam basic. From a previous JSON data file created from PDFsam, if I try to open PDFsam from there, it doesn't seem to take that as input for the merge function.
Am I missing something? Might this be considered for PDFsam.
Environment: PDFsam 5.x on Windows-11 (but also happened with PDFsam 4.x and with Windows-10).
With Windows, a general workflow is that if there is a data file of a particular type (typically, file extension), then simply double-clicking that data file will open the application, and also that data file will then be the input and default output for that application. (There are variants, such as mouse-hold and select "open with" but the same semantics of "use this [data] file as data input" still holds true.)
This doesn't seem to be the case with PDFsam basic. From a previous JSON data file created from PDFsam, if I try to open PDFsam from there, it doesn't seem to take that as input for the merge function.
Am I missing something? Might this be considered for PDFsam.