View Single Post
Old 08-13-2019, 09:01 PM   #19
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,801
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by DiapDealer View Post
I fear the situation is much more dire. In fact, I'm honestly not certain .bat|.cmd files ever worked with the Open With feature before Windows 10. Something with Windows 10 seems to have changed, but all examples of using QProcess::startDetached() to run batch files on Windows that I've run into seem to suggest that it's "cmd.exe" that needs to be launched. And that the batch file needs to be one of the arguments to cmd.

Something like:

Code:
return QProcess::startDetached("cmd.exe", {"/k", "C:\Path\to\mybatchfile.bat"}, "C:\Working\Dir");
If true... then the Open With feature of Sigil is going to need a bit of an overhaul to support launching exes AND bat|cmd files on all supported versions of Windows.
But the "Open With" feature is there from years. Someone before must have faced the issue of running a program with a switch, from Sigil, and under Windows 7. So, if it were an old "bug" (it doesn't seem a bug according to your words), already someone would have written about it.
RbnJrg is offline   Reply With Quote