@Kent-Dorfman OK, I do respect your personal feelings / opinions about Bluetooth in Linux. That really does not answer my question - even if is not strictly QT - how do I instruct / code Bluetooth Linux QT QSerialPort to have an option to set the data parsed by Bluetooth using to RS232/EIA I232 configuration / format. .
Here is a snippet of QT documentation I am trying to understand and code:
Exchanging Data Between Devices
The more flexible approach for communication between two Bluetooth enabled devices, is to create a virtual serial port connection and freely exchange data over that connection. This can be done by the Serial Port Profile (SPP). The Serial Port Profile emulates a serial connection over the Bluetooth transport protocol RFCOMM.
To be able to receive incoming SPP connections, you need to listen to incoming connections using QBluetoothServer.
@Imeshsps found this which says,
If you use Qt Quick Studio Components or Effects in your project, you have to check out and install the Qt Quick Designer Components module from Qt Code Review.
It compiled succesfully but
cmake --install .
gave
-- Install configuration: "RelWithDebInfo"
didn't seems to do anything. Found libQuickStudioEffects.a file in build folder. Please can anyone help me with this?
Thanks.
Hello this is Gulshan Negi
Well, Squish is a software tool used for automated GUI testing of applications developed for various platforms such as Windows, Linux, macOS, and embedded systems. Squish offers several certification courses for software testers, developers, and managers to enhance their skills in automating GUI testing using Squish. These courses include:
Squish Certified Tester (SCT)
Squish Certified Engineer (SCE)
Squish Certified Manager (SCM)
The courses are designed to provide hands-on experience, theoretical knowledge, and certification upon completion.
Hope it will help.
If you haven't yet noticed, the new Qt Learning Center has been published at qt.io/learn. 🚀 From there, you can find our new course catalog and other materials related to learning Qt.
We also updated the Forum a bit: The Education and Certification section is now Qt Learning, and there you can find this new sub-category Qt Courses. In the sub-category, you can share your learning projects, ask questions, and learn from each other - please don't hesitate to post!
Courses at qt.io/learn are free and don't require logging in.
The first materials focus more on UI design, but fear not – we will soon also take Qt Creator IDE as a starting point and dive more into the world of backend development.
Right now, you can find general courses about Qt Group and its products, licensing, and installing Qt.
Your first mission is to create a simple To-Do application - for that, the course provides step-by-step instructions.
You can also learn more about 2D UI design and create this UI (or your version of it):
Each course contains a feedback form for anonymous feedback, but you can also give us overall feedback or learning topic suggestions with a form that you can find at qt.io/learn.
Blog post
Happy learning!
Thanks for sharing!
Regarding 1) and 2) - git is my preference.
(Comes with a handy advantage: When you find a way to make Qt even better, you can just push it ;-)
@ds3216 said in qprogessbar question!!!:
is being updated normally
What do you mean by that? The most common approach I know, is to do some work inside a loop and call setValue() on the QProgressBar. Usually, that loop is inside the main thread which also happens to be the GUI thread. This basically prevents the event loop from handling the update of the progress bar. The easiest way to test this is to put QApplication::processEvents() right after calling setValue() (or setFormat()). This is not the best solution and will heavily slow down your application. So, don't leave it inside your code. Once you confirm that this is the problem, we can help out with a better solution. In that case we would need more context how and when you are calling setValue().
This thing? As the tool tip suggests, it's supposed to alert on unread messages. There's a "mark read" combo box in the upper right of the page it brings you to.
As for its utility, that's my preferred way to browse the forum. I'm generally only interested in active discussions. Sometimes after marking everything read, threads that don't have any obvious new content reappear.
