https://bugs.kde.org/show_bug.cgi?id=408240
--- Comment #21 from Nikita Sirgienko <warqu...@gmail.com> --- (In reply to vialav from comment #20) > I would be grateful for some guidance which lines of code in Cantor has > changed from 1 June which are responsible for Qt signalling, so I may try > to chase it down in my backport, if you don't mind. All changes from June 1 with signals $ git diff HEAD..68cfbad2de0257a7bd96406a94b49ba5e0f25c13 | /bin/grep connect + connect(m_process, &QProcess::errorOccurred, this, &JuliaSession::reportServerProcessError); + disconnect(m_process, &QProcess::errorOccurred, this, &JuliaSession::reportServerProcessError); - // connect(m_expression, &Cantor::Expression::statusChanged, this, &PythonCompletionObject::extractCompletions); + connect(m_expression, &Cantor::Expression::statusChanged, this, &PythonCompletionObject::extractCompletions); - // connect(m_expression, &Cantor::Expression::statusChanged, this, &PythonCompletionObject::extractIdentifierType); + connect(m_expression, &Cantor::Expression::statusChanged, this, &PythonCompletionObject::extractIdentifierType); + QObject::connect(&inputTimer, &QTimer::timeout, QCoreApplication::instance(), &QCoreApplication::quit); + connection = QObject::connect(&inputTimer, &QTimer::timeout, routeInput); + connect(m_process, &QProcess::readyReadStandardOutput, this, &PythonSession::readOutput); + connect(m_expression, &Cantor::Expression::statusChanged, this, &PythonVariableModel::extractVariables); -- You are receiving this mail because: You are watching all bug changes.