These require a terminal emulator that supports VT100, which almost all linux terminal emulators do. Windows Command Prompt doesn't support them by default, but at the bottom of https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences there is some code that shows how to turn that on (it's only a few lines of additional code that you only need to run once at the beginning - I would put it into an #ifdef __WIN32 #endif for platform independence.)
I haven't actually tried that though and I'm not sure on which versions of windows it works.
Regarding python: python doesn't natively support VT100 either, but the colorama package https://pypi.org/project/colorama/ enables them (to my knowledge, it replaces the print or write methods with something that extracts the escape codes and does the manipulations via calls to kernel32.dll methods).
@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 ;)
thread = new QThread(this);
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
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.