General and Desktop

Setting the edit trigger comes to mind.

Upon further inspection, it turned out that the problem only occurs when the widget containing the QGraphicsView has the attribute Qt::WA_TranslucentBackground set. setAttribute(Qt::WA_TranslucentBackground); Is this really the intended behaviour or might this be a bug?

@Christian-Ehrlicher Thank you for help! Solution was found. I just missed in my garbage code, and i did't totally understand what i was doing for a lot of time.))))

@Paul-Colby [image: e8e9a52b-762a-473f-9f5d-f41dec1168f2.png] Sorry it's in french but you can translate to : qt module not found(qtserialport).Import paths: D:/QTINSTALL/5.15.2/mingw81_64/qml I built this projet using this option (this is the window to build another projet but i did the same on the projet im working on) : [image: 70d41c33-1aeb-49ff-a73d-019b90f2292a.png] This is my output : [image: 02ece0c3-422a-46b4-a08e-91ec6b3b0f6e.png] This is my MakeFile from the build folder of the projet : https://pastebin.com/uKC6ydqB This is my Makefile.debug from the same directory : https://pastebin.com/xcWnN7v4 This is content of the import path : [image: 0c230972-75a9-4cd0-a73d-946e9e75a425.png]

@Christian-Ehrlicher Sorry, that not possible for me. Neither systemd-analyze nor PyMuPDF get_svg_image function (https://pymupdf.readthedocs.io/en/latest/page.html#Page.get_svg_image) are able to strip down SVG output to a QT compatibility level... When there is no other possibility, I think I have to change toolkit or wait until QT will adopt more SVG functionality some day.

@GeorgiosKoropoulis If you want to use whatever SQLite constructs in queries you have, like INSERT OR IGNORE INTO ... or SELECT ... FROM/VALUES (SELECT ... FROM), you can but you have to build the text of the query yourself. In this case you may find that binding does not work (that is supported by the driver, so depends what that allows for binding), but you can build that yourself into the text of the query without using binding. Just beware of correct syntax (e.g. quoting) and SQL injection.

I would try with the pre-compiled Qt libs + MinGW from Qt first.

Hi, How are you currently implementing it ?

@Joe-von-Habsburg There are, I assume, numerous online product activation services like LicenseSpring (no affiliation or recommendation). You could roll-your-own with something like Partial Key/Serial Validation or something similar.

@DeadSo0ul You don't have to use a layout in the content widget but absolute positioning is generally harder to maintain.

@Christian-Ehrlicher said in Migration from Qt 5.15.7 to Qt 6.7.0 and a small problem with QTreeWidget: windowsvista Thanks! so stupid I didn't try that... Perfect with WindowsVista

Changing to the previous minimum required version of cmake fixes this: CMakeLists.txt cmake_minimum_required(VERSION 2.8.6) #cmake_minimum_required(VERSION 3.16) src/core/player/mpv/CMakeLists.txt cmake_minimum_required(VERSION 2.6) #cmake_minimum_required(VERSION 3.16) Seems to be this policy: https://cmake.org/cmake/help/latest/policy/CMP0065.html This fixed the issue with cmake 3.4+: set_target_properties(yarock PROPERTIES ENABLE_EXPORTS TRUE)

Dependency Walker is very old so you can be happy that it even starts. And it is not a profiler.

bumping this up. Anyone can hint me how to mass paint controls?

@QtUser467 You don't want to encapsulate, and add a child. Not that I have ever used it, but use QGraphicsPathItem. Subclass that for your additional information. That will a QGraphicsItem. QGraphicsObject is a QGraphicsItem plus a QObject, usually so you can use signals/slots or maybe properties. You can also provide much the same if you need it by multiple-inheriting from a QGraphicsItem class and a QObject. Don't do so unless you need it.

@JonB Far be it from me to ask you for basic lessons (sorry for my often naive questions) but I've only recently started learning C++ again and a lot of reflexes have been lost. So thank you in advance for your patience, I'm improving (I think) a little more every day ;-) And thank you of course for all your tips and advice :-)

@JonB Thanks for your reply i will follow the links that you provides.

@Christian-Ehrlicher A QIdentityProxyModel is derived from QAbstractProxyModel per my first bullet :) Yes, one would start from a QIPM as an example of a QAPM (does the groundwork for all the identical columns) and just change the one column whose values need mapping.

@JonB Ah! Thanks for the heads up, will look into it further.

@Tom-asso said in C++ can't find ButtonGroup?: Brilliant! How in the world did you know that? The example immediately above the warning. Regarding the Warning about 'manipulating' QML from C++, my C++ code is only establishing a slot for the ButtonGroup signal, which seems a pretty standard way to do things in the Qt world. Yes. Using the standard QObject mechanisms is OK. Doing something like this (from a little further down the same page) is not: //bad code QQmlComponent component(engine, "MyButton.qml"); PushButton *button = qobject_cast<PushButton*>(component.create()); button->m_buttonText = "Click me";