Qt 6

Well, I guess I'll have to wait for Qt 6.1 or compile it myself ;/

Hi,

Did you add/remove the Q_OBJECT macro from your class declaration ?

Is this a slot ?

Thank you. I figure out that I mis-spell QComboBox in the stylesheet and that is main cause of the problem. Eventually, I get the result that I want and this is the code that provides it.
d52b79c6-4db5-4a5b-b91b-aa79fddbac29-image.png

ui -> comboBox -> setStyleSheet( "QComboBox{" "background-color: rgb(238,238,238);" "border: 1px solid black;" "border-radius: 25px;" "width: 40;" "height: 50;" "}" "QComboBox::drop-down{" "border-width: 0px;" "margin-left: 0px;" "}" "QComboBox::down-arrow{" "image:url(://Button_Icons/down-arrow.png);" "width: 10px;" "height: 50px;" "}");

Thank you! This has been very helpful to me :)

Thanks a lot, SGaist

And forgot to mention I figured out the solution to my problem. I had over-specified 'pythonpath in the 'system variable' of the advanced setting which caused the gdb to be unrecognized. when I removed the pythonpath ("something that separately prioritizes language environment") completely then it detected gdb in cmd and Qt. I hope it will help somebody with the same problem. the partial credit goes to a post in StackOverflow which mentioned gdb won't function if the python environment mistakes the actual path even though both normal path and pythonpath are derived from a single installation and single location (which in my case was the python 3.7 only nothing else). The root thing goes to gdb dependency on python scripting extension as was mentioned in Qt guide of debugger installation.
Here goes my windows
error.jpg

error1.jpg

@Beginner_to_code said in How to plot graph and its value in a tab widget?:

I need to plot a graph

Take a look at https://doc.qt.io/qt-5/qtcharts-index.html

@VRonin thx

Is there a platform independent alternative

See https://forum.qt.io/topic/125967/possible-qt-6-03-bug

should I switch development to 5.15 for now?

My personal opinion expressed here: https://forum.qt.io/topic/126005/qt-6-version-readiness-for-using-when

@SGaist I am getting back to this problem; however, to do so will mean that I will need to remove Qt and the Qt3D that I painfully installed. I would like to move Ninja and Vulkan so that I will not need to build them, also. I would like to save conan3D which was the conan build directory, but will that not work when I reinstall Qt6? Any advise? I wish there was a workaround to this TexMaker problem.

Bug is confirmed.
QTBUG-91104 is the general issue being worked, QTBUG-92030 is your specific case.

If you need a workaround (works in the current dev branch) you can set up a custom theme to hold the icons you want to use.

See this example on how to setup a custom theme.
The icons you need to provide are:

"computer" "user-desktop" "user-trash" "network-workgroup" "drive-harddisk" "folder" "text-x-generic"

You could use Breeze or Oxygen icons from KDE if you need them

@Christian-Ehrlicher

thanks for the help. Your tips helped solve the problem!

Sorry, I didn't even see the qt6 link.
Thanks for the
inclusion link
I see that Qt Charts is rated "Not Ready" ATM.
I hope the bug I submitted Sep/2019 gets fixed.

Hi and welcome to devnet,

That would be a question to bring to the internet mailing list. You'll find there Qt3D developers/maintainers. This forum is more user oriented.

@Benoit-Thouy Please elaborate "compilation failed as the properties are not well defined"
The warning is issued by the Clang Code Model and can be squelched by creating a new Diagnostic Configuration (or use your existing one) in Options...->C++->Code Model->Diagnostic Configuration and adding "-Wno-string-conversion" to it.

@Christian-Ehrlicher Okay, my mistake. So, after letting the program run for about 24 hours straight. It reached about 3.5 GB used. I opened another application with high memory use that pushed the physical RAM usage to 98%. At this point, the application DID release about 2 GB and is now sitting at around 1.3 GB used, but it also caused the system to become unresponsive for some time, which was probably from the virtual memory swapping. Despite that, it seems like unacceptable and unexpected behavior for an application that simply runs a timer repeatedly to eventually take that much RAM.

@iddqd-0
I don't think you can do this for MySQL, other than rolling your own code.

Thread affinity is a hard concept.

QThread should be seen as a "thread handler". It has affinity with the thread that created it.

The actual new thread handles the run method. Whatever you create in that method will have an affinity with the thread handled by QThread.