@Redman cool 😎

This worked, thanks a lot! (And for Linux, I used the same repositories, with "windows_x86" replaced by "linux_x64".)

@Pl45m4 Here is a short video of the application showing the issue: https://github.com/letsfindaway/OpenBoard/issues/203#issuecomment-2595705681 The rubber is a pixmap cursor using QCursor. The circle is repositioned at each mouseMoveEvent. You see that it is lagging behind the cursor. The preview image to the left is the second view attached to the same scene. So you see, nothing complicated. And as I already said in the beginning: when I run the same program using Qt5, then the lag is much smaller, because the repetition rate of the mouseMoveEvents is higher. I have setMouseTracking(true), so that I get the events even when the mouse button is not pressed. And no, there are no further actions connected to the movement as long as the mouse button is not pressed.

I see, thanks for explaining.

@markleo said in Apart from the modules provided by the official website, are there any other third - party Qt modules? If so, is there a central repository similar to npmjs.org?: third - party Qt modules What are third-party Qt modules?! Modules not made by Qt devs and published in the official Qt releases are not "Qt"... Since Qt is still just a C++ GUI framework and still not its own programming language like JavaScript, there are thousands of projects made by users/contributors on GitHub and similar sites, which work with or add something to Qt... custom widgets, functions or just code snippets... Edit: What @ChrisW67 is referring to is what I meant..."extensions" like QxORM can be integrated because of Qt's C++ API... but so does every C++ library work with your C++ project

@SGaist Not a problem :) Just not sure what else OP wants.

Then you're lucky it worked :-) Good thing you can fix your QIODevice class !

@Deneguil said in Custom QGraphicsEllipseItem mousePressedEvent single clicks: @Asperamanca Thank you very much for your in depth breakdown of the event propagation pipeline. I originally wrote the following line to prevent both events from firing. if(itemAt(event->pos()) != nullptr) return; Without it it'd print both "GV clicked" and "State clicked". If modified it to this one now and it works perfectly. if(itemAt(event->pos()) != nullptr) { QGraphics::mousePressEvent(event); return; } Both strings are still printed without the return which is why it's still here for apart from that it's perfect. Thank you! However, this way you are bypassing a lot of things, which could lead to confusion the next time you'd like to add something. What you probably want (I'm guessing a bit here) is this: void GraphicView::mousePressEvent(QMouseEvent* event) { QGraphicsView::mousePressEvent(event); if(event->isAccepted()) return; std::cout << "GV clicked\n"; } Now you can catch the event in the item, handle and accept it. The view will know that someone has taken care of the event, and it doesn't need to consider it.

@Pl45m4 Thank you for your feedback, I'm fairly experienced with plain C++ but not very with Qt or using Valgrind with external dependencies so I was a bit confused about what was happening. I'll keep that in mind in the future!

@Gracy The question is pretty old, but i know the answer... First, make sure, the permissions are added. Maybe you are missing the following: https://doc.qt.io/qtcreator/creator-deploying-android.html#editing-manifest-files To check and request permissions you can do: QFuture permission_request = QtAndroidPrivate::requestPermission("android.permission.WRITE_EXTERNAL_STORAGE"); switch(permission_request.result()) { case QtAndroidPrivate::Undetermined: qWarning() << "Permission for writing to the storage undetermined!"; break; case QtAndroidPrivate::Authorized: qDebug() << "Permission for writing to the storage authorized"; break; case QtAndroidPrivate::Denied: qWarning() << "Permission for writing to the storage denied!"; break; }

Hi, GitHub is only a mirror of Qt's sources so what exactly did you install ? As for your project are you using something like cmake to manage your project ?

QTBUG-136489

The check in setColor() is not needed - if there is an oom the app will crash.