#288 Gunplot as QProcess

No Za — Tue, 07 Nov 2023 20:20:05 -0000

Thanks, this solves print to STDOUT!
But the other question, regarding how GP detects in which mode it is started, is not answered.

#288 Gunplot as QProcess

Hans-Bernhard Broeker — Tue, 07 Nov 2023 19:54:08 -0000

See "help set print"

Gunplot as QProcess

No Za — Tue, 07 Nov 2023 18:15:55 -0000

Hi,
I start Gnuplot as a QProcess

Gpt = new QProcess();
arg << "-s" << "<&0";
 Gpt->setArguments(arg);
 Gpt->setProcessChannelMode(QProcess::SeparateChannels);
 connect(
           Gpt,&QProcess::readyReadStandardError,
           this,&GpObj::ReadError);
    connect(
           Gpt,&QProcess::readyReadStandardOutput,
           this,&GpObj::ReadStdOut);
 Gpt->start("c:/cygwin64/bin/gnuplot-X11");

so far so good.

My problem is that only STDERR seems to be used for any output from gnuplot.
If I try to gather information eg. by print MOUSE_X," ",MOUSE_Y I have to check that this is the correct output and not an error from a preceding plot command, eg format error etc.
It would be really helpful if errors would go to STDERR while normal output goes to STDOUT
In this case eg. it is much easier to filter out "Press return for more: " during the help command and present the full text at once.

Is there a way to make gnuplot believe to be started interactively ? Or the other way around how to gnuplot detect that it is not called from bash ?

Recent changes to 288: Gunplot as QProcess

#288 Gunplot as QProcess

#288 Gunplot as QProcess

Gunplot as QProcess