C / C++ / MFC

Quote:

Forgive me to be so bold - but I just cannot believe that in versatile forum like
this there is nobody who can at lest give me some idea how to resolve this.
It seems to be a problem that everybody wants SINGLE system problem
- that seldom works in real life.
As the title suggest - I need to connect Qt generated object / window to Linux "terminal"
(operating system ) native window.
I can highlight ( Using Qt) the text in the native window (!)
but Qt gives me no indication it did that.



PLEASE - NO PASSING THE BUCK TO QT FORUM - THEY HAVE NO IDEA HOW TO PROCEED - IT IS NOT Qt ISSUE IN THEIR ASSESSMENT -HENCE out OF THEIR narrow minded LEAGUE.

ps i WILL REMOVE THIS , AND MY SIMILAR POSTS, IF i DO NOT GET REASONABLE REPLY , JUST TO SAVE SPACE HERE.

Edited / addendum

I am still looking for somebody who is willing to help me instead of just posting text.
If it bothers you that my post is not specifically C/C++ code , please ignore it .
If it bothers you that my post is too complex , please ignore it also.
If it bothers you that my post is poorly written - read how to post / answer questions.

Is short - write something helpful and constructive.

Member 14968771 wrote:

How does terminal created window "connect" to Qt ? - that is the question.

int value = 5;
do
{
// some stuff
} while (values < 10);

into" <<QString::number(winId())

<pre>        QProcess *process = new QProcess(parent);
        // qDebug() << "Windid " << QString::number(winId());
        processTERMINAL = new QProcess();
        QString exec = "xterm";
        QStringList params;




        params << "-T" << "bluetoothctl no options (interactive) case 0 +hold " << "-fa" <<"Monospace" << "-fs" << "14"<< "+hold" <<
                  //       "-into" << QString::number(winId) <<
//                  "-into" <<QString::number(winId())<<
    "-into" <<QString::number(child->winId())<<
                  "-e" << "bluetoothctl";

        qDebug() <<"params " << params;
        processTERMINAL->start(exec, params);
        if(processTERMINAL->waitForStarted())
        {
            qDebug() << " processTERMINAL->waitForStarted() OK";
            qDebug() << processTERMINAL->readAllStandardError();
            qDebug() << processTERMINAL->readAllStandardOutput();

            //process->size(100,100)
            //processTERMINAL->open();
            //process->write("help\n");
            //ui->textEdit_124->append(process->readAllStandardOutput());

        }

Member 14968771 wrote:

how to "link " Qt process created terminal window with Qt running application.

Processes have two predefined output channels: The standard output channel (stdout) supplies regular console output, and the standard error channel (stderr) usually supplies the errors that are printed by the process. These channels represent two separate streams of data. You can toggle between them by calling setReadChannel(). QProcess emits readyRead() when data is available on the current read channel. It also emits readyReadStandardOutput() when new standard output data is available, and when new standard error data is available, readyReadStandardError() is emitted. Instead of calling read(), readLine(), or getChar(), you can explicitly read all data from either of the two channels by calling readAllStandardOutput() or readAllStandardError().

<pre>int CCC_MdiChild::readFromStdout()
{
#ifdef TRACE_MDI_XTERM
    qDebug()<< "TRACE_MDI_XTERM  "  <<Q_FUNC_INFO;
    qDebug()<< "TRACE_MDI_XTERM  @line "  << QString::number(__LINE__);
#endif
    QString TEST = QTextEdit::toPlainText(); //::text();
    qDebug() << "TEST " << TEST;


    QTextStream out(stdout);
    qDebug()<< "read all " << out.readAll();
    out << QString("Some text");

       QTextStream in(stdin);
    qDebug()<< "read all " << in.readAll();
    out << QString("Some text");

Member 14968771 wrote:

do not get so huffy.

, you have pointed that out yourself and it helped immensely ,

Member 14968771 wrote:

you are avoiding to provide a solution.