General and Desktop

@JonB Thank you.. I followed QStandardPath and tested in different target systems. It is able to create and write into the files independent of directories

@pocruadhlaoich ah ok, this I don't know, sorry.

@Lahearle glad to help. If you have more questions pertaining to your original ones, feel free to ask; otherwise consider marking the topic as solved.

@SGaist Thanks for pointing me in the right direction; it looks like what I am after is KDesktopFile.

@ChrisW67 thanks for that. Still seems very clunky and time consuming. I have written a short program that finds the correct module. I'll post this separately. cheers Mick

Hi, Are you sure your database connection is still opened when arriving in the cleanup function ?

@Christian-Ehrlicher That would be ideal, but QMake was the system used when the project started. We're considering porting everything to CMake, but it looks like it's going to take some doing. @Pl45m4 I tried to use the search function, but those seem to be good sources that I hadn't seen yet. I'll take a look at those right now. But I was able to find an answer on StackOverflow that I somehow missed until now: https://stackoverflow.com/questions/32279193/cuda-win7-qt-creator-lnk1104-cannot-open-file-cuda-file-obj I just copy-pasted it and it worked (after changing the version number from 7.0 to 12.1). Then I used the code I pasted above and it worked. Then I used a legit CUDA program and it worked. So I'm going to go through it line by line to understand why that .pro works. Thank you for the links!

@rdowell does not cost anything. Simply go for it.

@ivanov-ivan At Qt 6.5.0 works code like this: m_pHttpServer->route("/websocket/<arg>", [this](const QString &arg, const QHttpServerRequest) { qDebug() << __func__ << request << arg; return QFuture<QHttpServerResponse>(); });

@QtsCOde No worries. If installer UI was better there would be no need for such questions ;-)

@JacobNovitsky The command to execute your program after launching gnome-terminal is added by Qt Creator. following the -e or --command flag. See the gnome-terminal man page The --geometry flag is a little vague. The size components are either in pixels or characters depending on the application. The man page does not shed any light on this and I do not have it to test. Have you tried the command from a shell prompt? /usr/bin/gnome-terminal --geometry 80x24+2720+0 -e /bin/bash # or /usr/bin/gnome-terminal --geometry 800x600+2720+0 -e /bin/bash You can also try it with a single hyphen before geometry rather than two. If the window cannot be placed 2720 pixels from the left of the screen then I would expect it will usually be moved somewhere it can fit.

@SGaist Just for information and if you are interested. After weeks of daily use of ksensors qt/kde 4, I started porting it to qt/kde 5. This time there are a ton of changes in the cmake configuration, in the kde api (several things have been eliminated, you have to use qt directly or rebuild from scratch) and some in qt (a few things even if delicate). It's much more difficult and heavier than I had hoped, on the other hand the progress is much faster, in leaps. After this port I would say that ksensors has definitely entered on modern/recent projects, at least more than many others.

@Christian-Ehrlicher Thanks Christian, fixed adjusting slots.

Use proper export macros and/or create a cmake bug report. Using the correct macros will also help the compiler / optimizer and the link & loading speed on linux. /edit: See the documentation about static symbols - so no need to create a bug report.

@JonB It would be a bug since the schema is file:// (two /) and the path is /foo/bar. And since the path must always start with a / it's file:///C:/foo/bar - everything else is wrong.

Ah I understand. I even managed to add them manually via add_dependency in my CMakeLists to the main target and now they are build every single time. Thanks for your support!