I have a basic QAction set up as a sort of test action: actions_.network_ping_ = new QAction(tr("Ping"), this); connect(actions_.network_ping_, &QAction::triggered, this, [this] { osc_service_->send(EosOscMessage::ping()); }); Whenever I trigger this action, it works as expected, and does exactly as prescribed, but then my program crashes with an error that I don't know what to do with: PaletteRepo(74405,0x16d1ab000) malloc: Corruption of free object 0x14402bb90: msizes 25903/0 disagree PaletteRepo(74405,0x16d1ab000) malloc: *** set a breakpoint in malloc_error_break to debug This still happens if I rewrite that lambda in the connect call into a slot. If I set a breakpoint and step through, it takes me to qobjectdefs_impl.h, specifically line 116: template <typename, typename, typename, typename> struct FunctorCall; template <size_t... II, typename... SignalArgs, typename R, typename Function> struct FunctorCall<std::index_sequence<II...>, List<SignalArgs...>, R, Function> : FunctorCallBase { static void call(Function &f, void **arg) { call_internal<R>(arg, [&] { return f((*reinterpret_cast<typename RemoveRef<SignalArgs>::Type *>(arg[II+1]))...); // < This line }); } }; I'm not super familiar with malloc so I don't know what malloc_error_break is or how to set a breakpoint there as the error suggests. Does anybody have any guidance here? This is in CLion on macOS Sequoia.

Hi, You can also check out this library: 👉 QAudioTagReader It’s a Qt-friendly wrapper around TagLib for exporting audio tags.

In QT Design Studio, Tab Buttons are mostly for navigation within the UI, but each tab doesn’t automatically hide other content. Usually, a StackView or Loader is needed to switch visible content depending on the active tab.

@IamSumit can you reproduce the issue and share the Support Information logs. Please refer to the following Knowledge Base Article regarding how to obtain the Support Information is https://qatools.knowledgebase.qt.io/misc/collecting-support-info/collecting-support-information-linux-mac-windows/

Hi, everyone. I'm looking for a teammate or two for this competition

I do a lot of python/pyqt database access using psycopg2 for PostgreSQL. It's so much easier to prototype these kinds of ideas in a language like python, and if needed then port it to c++, but truth be told, most of the time the python app is just works as is so no need to rewrite in c++. For something as simple as you are alluding to, the hard core OO models using DAO/DTO are probably overkill. Also, when dealing qith SQL queries it's "nice" to work in a language that is NOT strongly typed. Sorry if this is a round-about way to respond. Your path has merit in the realm of intellectual curiosity, but if you want it done quickly then python is a better option, and you can still wrap it in a Qt GUI. Yikes! Didn't notice OP was 9 months ago...

Bonjour, Dans votre fonction, call, le device est détruit à la fin de la fonction, Le signal signalWithoutPointer ne peut pas marcher car cela demanderai un copy de l'objet Device mais il s'agit d'un QObject ou le constructeur par copy est désactivé. Le passage d'un pointeur vers Device, ben, la moment juste après le pointeur est null. Le passage avec signal sur pointeur "pointer", lui il marche mais c'est la responsabilité de la classe connection de détruire pointer (et donc de garder une variable dessus). Le plus simple c'est de faire un retour de fonction si vous voulez vous simplifiez la vie. // in Connection.cpp Device* Connection::call() { return new Device("Pointeur"); } //main.qml (à la place de la Connections) property Device device: Connection.call() Dans ce cadre cas là, par passage par pointer via un retour de fonction, l'objet appartiendra au QML et sera détruit par le QML Engine. Cependant, je recommande plutot de passer par une propriété. // in connection.h // je suggère de renommer cette classe en ConnectionController (pour éviter la confusion avec le type qml Connections class Connection : public QObject { Q_OBJECT Q_PROPERTY(Device* device READ device CONSTANT) public: explicit Connection(QObject *parent = nullptr); Device* device() const; private: std::unique_ptr<Device> m_device; }; // in connection.cpp Connection::Connection(QObject *parent) : QObject(parent), m_device(new Device("Pointeur"){} Device* Device::device() const { return m_device.get(); } // main.qml property Device device: Connection.device Ici le device reste la responsabilité de la classe Connection, mais c'est géré par le uinique_ptr. Si le device peut changer, il conviendra d'ajouter un signal deviceChanged et de supprimer le CONSTANT de la Q_PROPERTY pour y mettre un "NOTIFY deviceChanged".

Everything looks right in my eyes. If I e.g. search for @Volker-Hilsheimer's blog post about QRangeModel, I'll find it here. Do you have a specific link for me to check?