Hi, It is their problem if they have started relying on a bug.
I don’t think this is a good way to approach this. When programming with a framework, you program based on the current behavior of that framework, regardless of what the “correct” behavior is supposed to be. I think it's pertinent to pull an insightful quote from Linus Torvalds here: “If it’s a bug people rely on, it’s a feature” Don’t get me wrong, this is definitely a useful discussion (thanks for bringing it up), but as I see it in light of Qt’s compatibility promises, drastically changing drag and drop behavior looks like a Qt7 point that should be further discussed. I personally think Shawn’s proposal seems very sensible at a glance. If I recall correctly, there was a list of major behavior changes for Qt6. If we decide to change this behavior, this point should probably be added to the Qt7 equivalent if one exists, in addition to an eventual porting guide. Cheers, David Skoland On 7 Jun 2022, at 08:47, Laszlo Papp <lp...@kde.org<mailto:lp...@kde.org>> wrote: On Fri, Jun 3, 2022 at 11:08 PM Giuseppe D'Angelo via Development <development@qt-project.org<mailto:development@qt-project.org>> wrote: Given the blame on that code shows no changes since Nokia times, something just tells me that this has never worked properly and people started 1) relying on the release to be never received It is their problem if they have started relying on a bug. We cannot leave bugs around and stop fixing bugs because bugs have been released. Moreover, not only has this not been documented to rely on, but in fact, even the opposite has been claimed by the Qt docs, so people really should not rely on the opposite of the design and documentation: https://doc-snapshots.qt.io/qt6-dev/qdrag.html#exec "Other events are still delivered to the application while the operation is performed." So, I feel like it is just to just fix the code as the documentation claims the behaviour. So, yes, I agree with you that this is not something we should leave as is. _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> https://lists.qt-project.org/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
