Hi and welcome to devnet,

There's no ready made "console widget", you can use QPlainTextEdit or depending on the amount of data a QListView with a custom QStyledItemDelegate for fancy rendering.

For getting the output of your cli application, you can use QProcess.

correct @Paul-Colby
thanks

@CybeX
yes, I have the same problem sometimes.
I just uncheck it and check it again then run the program and it will work.

Hi,

As silly as it may sound but wouldn't removing << std::endl from the checking line be enough ?

@Bremenpl
Hi, other option is to create a custom session
so you can have single app and also be able to start a desktop if needed.

Most likely you will want to run a windows manager also.

http://askubuntu.com/questions/23932/how-do-i-replace-the-desktop-by-an-application

Im not sure if @Eeli-K solution is the same in debian version. :)

@SGaist Thank you, I will try it!

update
using native api, there are colors to some degree :)
https://msdn.microsoft.com/en-us/library/windows/desktop/ms682073(v=vs.85).aspx
check out
https://github.com/mattn/ansicolor-w32.c

but your app is then tied to windows :(

By the way, in QApplication's detailed documentation, you have an example of how start an application in "no-gui" mode.

@hskoglund Thanks for the info

I don't understand what you mean, Qt is a GUI library by design.

@dcape yeah, you're absolutely right. thanks for your efforts. I was thinking about conflicts and checked widthChanged() with auto-completion - this is why i decided not to change the title of js function. Thanks, again ;)

Oh, then it has nothing to do with a console or a console. qDebug is a text stream.

To redirect output of qDebug use qInstallMessageHandler.

Build and install QTerminal, then you can use it like other libraries

If it needs a named pipe then you should ask the author.

AFAIK, you should be able to connect to a named pipe using QLocalSocket

@Varius said:

thread = new QThread(this);
console->moveToThread(thread);

IIRC, these lines are doing more than you think they do. thread's parent is your object, then you move your MyObject instance to thread, so all objects who are child of your MyObject instance are moved the thread. So thread will be moved to itself.

All in all, you should rather have thread in your main as a stack object