Qt Creator and other tools

@Pl45m4 tried to install manually but failed!

@roy815 said in How in the Centos system of QMainWindow QDialog add Qt::WindowContextHelpButtonHint:

setWindowFlags(Qt::CustomizeWindowHint|Qt::WindowContextHelpButtonHint | Qt::WindowCloseButtonHint );

You're overwriting the flags, it should be:

setWindowFlags(flags() | Qt::CustomizeWindowHint|Qt::WindowContextHelpButtonHint | Qt::WindowCloseButtonHint );

Also, is for dialogs and you should read the documentation:
"Adds a context help button to dialogs. On some platforms this implies Qt::WindowSystemMenuHint for it to work."

Solved by updating Qt:

image.png

image.png

@Pl45m4 I apologize for my incomplete explanation. What I meant to say is exactly this:

I created a project and build/run settings which includes path of destinations, executables and qmake settings. When I publish my project to another person all the settings I created are missing. As you said pro.user file shouldn't shared between projects or used on other systems. But As I read in qt documents it says pro.shared file could be shared for make projects settings portable. The problem is I wrote this file and I can share my settings to another system, but every time I need to change the version and set the current path of project for build/run configurations.
Here is an example:

C:\Users\duruk\Desktop\Sample\build

This is the target path of my Press_Release build configuration. As you see this path is unique for my system (name of project is Sample, this folder contains pro file and pro.shared file). I have written a bash file to changing the paths to current paths, and a manual for describing how to user could set configuration. This is the bash file I wrote to changing paths:

DOSYA="Sample.pro.shared" OLD="xxxxx" NEW=$(PWD) if [ ! -f "$DOSYA" ]; then exit 1 fi sed -i "s|$OLD|$NEW|g" "$DOSYA"

Well now I'm searching a way to settings project path automaticly and and prevent changing ProjectExplorer.Project.Updater.FileVersion variable every time project moved another system. Is there anyway to share settings more easy and effective?

The documentation of the method I tried:

https://doc.qt.io/qtcreator/creator-sharing-project-settings.html

Thank you for your reply.

I have installed Qt 6.8.1 (before I had 6.8.0) and I have no problem.
Thank you (I am French and my english is wery little or bad)

The same for Qt Creator 15.0.0-rc1 (14.0.84) that I've downloaded here: https://github.com/qt-creator/qt-creator/releases

@Christian-Ehrlicher said in Change build directory with cmake:

cmake does not place anything anywhere without question. It does what it gets told. Maybe you configured QtCreator (you did not tell us what you're using as IDE) so that the build dir is somewhere else, I don't know.

I'm using Qt Creator 14.0.2.
Anyway, there is no need to restart from scratch. It was enough to remove the kit from Build&Run and select it again.
It seems the chaning of the build directory is not working, at least on my installation.

I have now successfuly installed the online installer for Qt6 on a fresh Pi OS64. I had to install some dependencies including some to get the online installer to run without crashing.

From the Installer, I selected custom install, selected an older Qt6, then selected the components I required including Qt Creator and debug symbols. The online install then proceeded to completion without problems. QtCreator was added to the Progamming Menu making it easy to launch.

I am back to being able to run the QtCreator debugger and view items like QString correctly, although it took me several days of frustration to get there.

I planned to detail the dependencies I installed but this forum thought it was spam.

@Julius: Indeed that works by pressing the Alt key when the cursor is in a variable and Edit > Preferences > Text Editor > Behavior > Mouse and Keyboard > Show help tooltips using keyboard shortcut (Alt) is checked.

Regards

@osirisgothra said in Never (ever) refactoring class to "separate set of dedicated source files" ever again:

Long story short, I lost a whole days worth of work

That's why there are version control systems like Git out there.
Just commit your changes regularly, especially before doing bigger/risky changes.

What you describe sounds like a bug in QtCreator, you should create a bug ticket in https://bugreports.qt.io/secure/Dashboard.jspa

(Disclaimer: I have not yet tried to use qmllint myself. I previously described my own method to "ban qml warnings" here: https://forum.qt.io/topic/113028/is-it-possible-to-use-any-qml-parser-tool )

There is an open Qt bug with title "How to use qmllint on multiple components in one project" here: https://bugreports.qt.io/browse/QTBUG-120442

That bug report seems perhaps relevant? There are a lot of comments there. Maybe some will give you clues.

It looks like consistently moving the include of Pybind11 headers before QT Headers has fixed it.

However, this also goes for the full include tree. So if A includes B, and B includes Pybind, A should include B before including any QT Headers (QObject, QProcess, QVector, etc)

Not a beauty to handle, but at least a way to make backups. Thanks!

@Calvin-H-C
There has been no QScrollView since Qt3. I have not heard of requiring two children for adding a layout, but there you are. Not everything needs a layout --- containers like QScrollArea do not, I don't think you should put one on them, and should not show the "no entry" sign without one. For scrolling issues I know that QScrollArea has a widgetResizable which often needs setting to true for scrolling/scrollbars to work right. Otherwise show a screenshot from Designer and paste (a minimal) .ui file and someone will doubtless comment.

@jsulm I used Qt Installer. It is installed in C:\Qt

I am not entirely sure what your problem is in this case. However, for general use of Qt in VS: Do you have the natvis debug helpers installed (https://wiki.qt.io/IDE_Debug_Helpers)?

What might be the case with your problem is that you don't have debug symbols for Qt installed. My guess is that maybe you need to install the Qt source using the online installer. Though I'm not entirely sure about that.