General and Desktop

@Mounish Is the driver string you show for Microsoft SQL Server? (If so, I hadn't heard of Uid= or Pwd=, but there you are.) Whatever it is for, what does that database driver documentation say is the syntax for using Win Auth?

@SGaist Hi, I am using Qt Creator 4.13.1

I'd say the chances are very low. Qt is deprecating it's own algorithms in favor of all the goodness found in STL nowadays.

"-j [jobs], --jobs[=jobs] Specifies the number of jobs (commands) to run simultaneously. If there is more than one -j option, the last one is effective. If the -j option is given without an argument, make will not limit the number of jobs that can run simultaneously. "

@Pablo-J-Rogina ``` QSqlQuery query(QSqlDatabase::database("QTUSERS")); to QSqlQuery query(QSqlDatabase::database("MyConnect")); and ``` query.prepare(QString("SELECT * FROM Users_QT WHERE username = :username AND password")); to ``` query.prepare(QString("SELECT * FROM Users_QT WHERE username = :username AND password = : password"));

Hi, That's something you should talk about with the Qt Company directly.

Hi, One possible way is to use QRegularExpression::match or since it looks like xml, you can use QXmlStreamReader.

Hi, By instinct, I would say look at the mouseMoveEvent method. Taking a look at the code of QHeaderView, I don't think it's something you'll be able to do by just subclassing.

@Pl45m4 Thank you so much. I set it to "This" and my code worked well.

@JonB Thanks! In the future I will add some sort of editing feature, but for now it will just be viewing.

@SGaist I did not say that there is a bug, to be honest I was quiet sure that it is me who is doing something wrong. And yes - I tried Bluetooth Serial Terminal (from Win10 store) and it also takes a few seconds to connect to device as well. I assume it might be the device (it is a custom thing I'd say) that lags on open. Alright, at least I understand now that either I need to move all the stuff to some kind of worker handling QSP on separate thread or accept that there will be a lag on open. Thanks, guys!

@JonB said in How to check if no treeitem is selected in the tree view: Is that subsection new in the docs, in the past I didn't find that explanation? It's already there since some years... :) https://doc.qt.io/archives/qt-4.8/model-view-programming.html

I would start with a clean source (make sure there are no generated files) and build dir

@jsulm QTouchEvent class has the method *QTouchDevice QTouchEvent::device(). The device type QTouchDevice::TouchPad is supported by QT. So If I understand QTouchEvent documentation correctly, it should be possible. Access to the multitouch data from multi-touch-capable precision touchpads is possible in Windows via a low-level Window's API (e.g. GetRawInputData()). I was guessing/hoping that QTouchEvent was a higher-level, multiplatform solution on top of this.

@SGaist @JonB thanks. I have to get previously generated element using QDomNodeList in next iteration and then I can append correctly for each timestamp and device.

@Adithya said in Execute commands in git bash using QProcess: And yes my intention is to run multiple commands in one session of git bash (That was the reason I was trying via write().) . Then we need a couple of minor modifications your original code: process->start("C:\\Program Files\\Git\\git-bash.exe", QStringList());, or process->start("C:/Program Files/Git/git-bash.exe", QStringList());. No arguments, though you should check the git-bash documentation to see if that wants any special arguments for your case where its input/output is piped. process->write("ls\r\n");. Your order of the CR-LF is the wrong way round. I don't know whether you need the \r, or even if that will upset it and it wants \n only. You might want a "flush" after each write. You call process->readAllStandardOutput() immediately after waitForStarted(), that is/could be too early. You only call waitForReadyRead()/readAll() once. That is (potentially) not enough, output could come back in multiple, separate chunks. You are relying on the output from the bash/command all being flushed from the other end for you to receive it. You had better hope their implementation does that! If you notice only partial data back to you, this could be the reason. You are using the ("nasty") blocking/synchronous waitFor...() calls. If you run into trouble this way/things don't behave as you expect, change over to the asynchronous signals/slots methods of QProcess. Don't forget to close your process/free it!