General and Desktop

@Dekken as suggested by @eyllanesc both the indexFromItem & itemFromIndex are protected fucntions..

just delete the projectname.pro.user and so you can select the kit installed ...easy to go from windows or linux to MacOS this way @NielsHolst said in Wrong default configuration of clang++ kit on OS X: I have found the reason why Qt Creator could not configure my project correctly: My .pro file depended on an environment variable. Moving from Windows to Mac and being unable to set an environment variable on the Mac (!), I resorted to set the environment variable from within Qt Creator. However, to be able to set the environment vaiable in Qt Creator, I had to first open the .pro file and let Qt Creator configure the project. That configuration could not be carried through correctly because the environment variable was not yet defined. Then when I defined the environment variable, and the .pro file should be OK, Qt Creator kept the faulty configuration. The way out was to rethink my project file and rid it of its dependency on the environment variable.

@JonB the same result. Memory leak increases with 100 KB/s rate... UPD: Hm.. 'Leak' has stoped on 8MB....

Then start by running the configure script, it's a requirement in order to build qtbase at least.

@VRonin said in QTreeWidget: get QTreeWidgetItem* by internal widget: You just need to reimplement paint() and fill a QStyleOptionButton to to show the button Hi! Is it possible to show ComboBox and CheckBox as you wrote?

@SGaist Thanks for reply.

@JonB I believe this answer solves the problem I described above.

Thanks, I will try that

@SGaist yes of course. I think this is the answer to my question https://stackoverflow.com/questions/66828571/mime-hasimage-returns-true-but-mime-imagedata-returns-none-on-linux

@Detzi Hi Well the red layouts are meant to be used to sub divide another layout and it not used as base layout as they float if not put in a layout. So normally we apply a layout by right-click the widget and use the layout menu.

@bogong No it's not a Qt bug. (The message isn't even generated by Qt, it's generated by your compiler.) If you read the message it tells you why the path is non-portable, doesn't it? specified path differs in case from file name on disk [-Wnonportable-include-path] Will work under e.g. Windows, will not work under e.g. Linux. Hence "nonportable". And it tells you what to do about it: either switch off the -Wnonportable-include-path warning, or (better) change your include statement or the case of the file/path name on disk to match each other.

ok, I think I've messed up in the order I'm creating the widgets...will report back when I confirm it.

@linuxfever said in Propagate mouse clicks through a transparent widget: event->accept(); @linuxfever comment the event->accept(); line and test it, whether does this events propagates further.

Thanks. I think you answered the question, please feel free to add anything later if you want. I mark it as solved.

Hi, @summit said in Change in the path of the Qt headers .: include <Qdebug> You have a typo here, it's #include <QDebug>.

Adding to @JKSH, the qml option expects the path to the files in your project sources so it can parse them to pull all the required dependencies.