|
From: | Benjamin Szőke |
Subject: | [Octave-bug-tracker] [bug #56416] Incorrect octave.bat - missing MSYSTEM, usr\bin, qt graphics |
Date: | Thu, 30 May 2019 18:02:57 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36 |
Follow-up Comment #5, bug #56416 (project octave): Octave.vbs use the "octave-gui.exe --no-gui" and it is working well thanks to that correct path and any other declared variables. But, i can not use octave.vbs when i want to execute it from an own C program as a childprocess with pipe interface. Octave.vbs will start octave-gui.exe as a background process in a new cmd window (then exit), so that my own C program does not have any pipe connection to the octave-gui.exe. If i use the "octave.bat --no-gui" it is better because the bat file will run octave-gui.exe in the same cmd and it will be the same childprocess. In this case the pipe connection is fine and works well. In the past i never used any plots and figure printing and the octave-cli.exe was enough for my tasks. But now i need a correct qt graphics for plots in command-line octave, too. I think in the future a fixed octave.bat (with using octave-gui.exe --no-gui) should be better to a general executing method in MS Windows than the octave.vbs script. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?56416> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |