forum.qt.io

@DevMattew said in [MSVC/Qt6] Address Space Exhaustion during "Edit and Continue" after migrating from Qt3 to Qt6.8.3: I am not referring to a Qt-specific API or a framework feature. I am talking about the MSVC 'Edit and Continue' feature provided by the Visual Studio debugger. Ah, I see. I have no experience with this functionality, so I'll defer to those who do. If you don't get any clues here, try posting at the Interest mailing list where Qt engineers are active (you'll need to subscribe first): https://lists.qt-project.org/listinfo/interest

@Christian-Ehrlicher I tried to install a program Streamtuner-ng (can be found on github.com/IronWolve). I installed it according his instructions and requirements. It crashed on an illegal instruction. This program is written in python and uses PySide6. He required that PYSide6>=6.6. It installed 6.11 (I think) and apparently also installed qt libraries in a venv. In the end the program worked with PySide 6.9.3 (and thus Qt 6.9.3). Debian 13 uses apparently Qt 6.8.2. This all worries me because a next version of Debian (or an update) may not work at all on my old PC's. I completely accept that certain things go slow or do not run well on my PC's but I would like to be able to run a normal OS (like Debian).

Hi all, I'm using a Qt Creator 20.0.1, with Qt 6.11.2 MinGW 64-bit on Windows 11. Creating a new project following these steps: New Project -> Application (Qt) - > Qt Widgets Application -> Name: test -> Build system: CMake -> Details (no edit) -> Translation file (no edit) -> Kits (no edit) -> Summary: Finish. It creates a project that runs smoothly, but debugging causes a SIGSEGV. I didn't add any line of code on purpose, to make it reproducible: Does this happens to someone else? and how can it be fixed? Thanks in advance for your time

@SGaist Hi, i just happened to write my own names while following the tutorial, so there is no issue in the code base, however to duplicate the issue you can change the numChanged after NOTIFY to numberChanged and see what happens. Cheers

Hi, I would say no settings at all. If you want to maximise the number of platforms supported, just use the defaults from your Qt build which aims to cover the 90% of the market at the time of release. You have more explanation in th2 supported versions selection guidelines in the Qt documentation.

It's best to post a full self-contained example (C++ or Python) that demonstrates a problem when posting one rather than just a snippet. It helps people to help you more. That said, it is a clear artifact of how the QTextDocumentLayout class (an internal Qt class that implements paragraph layout for QTextEdit by default) is implemented. List bullets are painted "on top of" and outside the text block that contains the list item, and you can see that not only (what I assume is) the auto-deduced block text direction does not apply to the bullet, also the baseline alignment is wrong. There are many, many, bugs with more complex document layouts with it - RTL related and otherwise. Your one is already reported as https://qt-project.atlassian.net/browse/QTBUG-60544, and a quick search in Jira will come up with more. My advice, is that if you are serious about this project of an Arabic language word processor with complex layout support, you should look sooner or later into implementing your own subclass of QAbstractTextDocumentLayout. It is a dark art of sorts, and quite difficult, but the control is needed to reach the level of quality one would expect.

Change node.material = material; to node.materials = [material]; because the Model in QtQuick3D has a property called materials (a list), not a single material.

The your first issue is: making DataPort private in your base class means that none of the derived class will know about it. See the cpp FAQ about access rules.

The problem is not the number of draw calls, but that you are generating circles with 1024 segments instead of about 32-64,

Hi and welcome to devnet, From the phrasing, it seems you have a commercial license. In that case, you should contact the Qt Company directly. This forum is more user oriented.

@DSpUz said in How do those crazy Q Macros work?: there is no visible Object instance. There IS an object instance! The singleton is an instance. I do not quite understand how the so called "signal" can change value of a property A NOTIFY signal tells the QML engine to discard the old (cached) property value and read it again. When your Globals singleton (instance) emits the numberChanged signal, the QML engine re-reads Globals.number and updates the text.

@IgKh yes this is the bug, updating my system fixed it.