Re: qt terminal for windows : qDebug() problems

[Tatsuro M. <tma...@ya...>]

>> Two topic
>> 1) message related to qt terminal in gnuplot main program.
>> 2) message in gnuplot_qt
> 
>I think you are correct.
> 
>1) The messages from qt_term.cpp can be written using fprintf(stderr, ...).
>This would be consistent with error messages throughout the main program.
>I will make this change.
> 
>2) Messages from the separate process gnuplot_qt should not try
>to write directly to stderr, since this may not go anywhere useful.
>qDebug() is supposed to handle this, but I can't help with how to
>configure on Windows.
> 
>Ethan


Thank you for the reply.

1)************************************************
>1) The messages from qt_term.cpp can be written using fprintf(stderr, ...).
>This would be consistent with error messages throughout the main program.
>I will make this change.


I appreciate that you will make the change.
All messages from qt_term.cpp will be represented not only gnuplot.exe but 
also wgnuplot.exe and wgnuplot_pipes.exe.

2)*************************************************
>2) Messages from the separate process gnuplot_qt should not try
>to write directly to stderr, since this may not go anywhere useful.
>qDebug() is supposed to handle this, but I can't help with how to
>configure on Windows.



>qDebug() is supposed to handle this, but I can't help with how to
>configure on Windows.

According information searched on the web, qDebug() on windows can be 
output messages to the console if the application is console one
otherwise message to send to the debugger if it is present.

gnuplot_qt.exe does not have own console.
This might be the origin represent nothing 
even if gnuplot_qt.exe executed from gnuplot.exe.

For gnuplot for windows, two alternative way can be considered
1) make original message system with qt tools within gnuplot_qt.exe.
2) transfer messages to the main process and represented in the main process.

I think that the case 1) is more practical than case 2). 

Tatsuro