Qt Creator and other tools

@Pagiraff That's interesting. You could check whether this is a known issue here: https://bugreports.qt.io/secure/Dashboard.jspa You can file a bug report if this is not yet reported (preferably with a small example project demonstrating the issue).

@xylosper Yea cmake can have some issues with certain ides. Others are built for it. The new MSVC 2017 has some support for cmake natively. My favorite ide CLion by JetBrains is 100% based around cmake and integrates completely with it. For things like adding a class and all that type of stuff. But if cmake isn't for you that is fine too. :) I'm not saying there's no way to do it with qbs, just that I haven't used it. Once I found cmake it's hard to use anything else. It handles everything cross platform, and all my development is cross platform. Maybe someone else can add on to the qbs thing...

@Kepler-141c This is rather a question for an Ubuntu forum.

This is 4.6.0 with CMake I believe 3.5.0.

WinRT ? You should have mentioned that earlier. Why don't use one of Qt's WinRT builds ?

@Snat Solve it using different approch Using argv to send either cin or pathway to fifo file. Then using ssh remotly with echo command > myfifofile. My code do the rest Reading from file or cin Hope this help

Apparently, recent versions of windows are now preventing any kind of automatic change to the taskbar: https://superuser.com/questions/1193985/command-line-code-to-pin-program-to-taskbar-windows-10 I tried the solution presented here for adding shortcut to the taskbar, but it didn't work. It probably used to work on older windows versions, but now, shortcut is created and added to the folded, but not visible on the taskbar. It's probably going to be difficult to change this, as it comes from windows side. The taskbar is the user's territory. Only he can modify it.

Hi, No, no problem having several versions of Qt Creator. Just keep them in separate folders.

Hi, Can you provide a minimal sample project that allows to replicate that ?

@koahnig Yes, I checked this page and didn't find the anwser to my question(((

@koahnig Thanks! It looks like it works

I've just added a usleep(100000) line prior to setting the direction of the GPIO, and I'm no longer receiving the permission denied error (but my application is now running very slowly!). As such I don't believe I have a particular issue with QtCreator itself. I'll leave this up in case anyone else has a similar issue. I'll be posting on SO now to try and resolve this permission/timing issue.

yes you're right , i did not "have" to restart the Qt creator, since you just add the location of corresponding qmake.

Solved the problem! The default working directory is the working directory as of the last time you closed the project (maybe save not sure). So I set the working directory to the new one by unchecking shadow build, closed the project, then re-opened it and the default shadow build working directory was updated. Now clicking shadow build works again. Somewhat unintuitive but oh well.

@tkansgar so please close this thread as solved now. thanks

@jsulm that that doc page refers to a specific class (QScxmlCompiler::Loader) which apparently was added subsequently to a class introduced in a earlier release (QScxmlCompiler, introduced in Qt 5.7). Evenso, apparently those classes cover another feature which is only orthogonaly related with generating source code from SCXML documents. Meanwhile, the Qt Creator's manual entry on Editing State Charts does not mention anywhere which Qt version is required to use this feature. This may cause some confusion as potential users may be led to believe that this feature just works, although it doesn't.

@sierdzio Thanks!

Since you mention functionality change: there is, of course, a way to use .pri cleverly. Consider this code: CONFIG += feature1 # ... feature1 { include(mySuperFeature.pri) } else { include(myOtherSuperFeature.pri) } In this simple way you can include different headers, sources, rules etc. based on some config values. However, even here, the pri file is only a simple include. You would get exactly the same results if you copy-pasted the contents of mySuperFeature.pri and myOtherSuperFeature.pri directly into the code above.