On 9/4/20 3:56 PM, Jérôme Godbout wrote:
Shouldn't the FileDialog belong to the Window and not to the editor? Try
without parent or parent to the top window on your dialog you can make it modal
if you need to lock down the window. That would prevent the editor destruction
to wrongly destroy th
Shouldn't the FileDialog belong to the Window and not to the editor? Try
without parent or parent to the top window on your dialog you can make it modal
if you need to lock down the window. That would prevent the editor destruction
to wrongly destroy the Dialog.
-Original Message-
From:
On 9/4/20 3:20 PM, Kyle Edwards wrote:
I now have a minimum working test case:
Err, looks like that got mis-formatted. Let me try again...
// BEGIN
#include
#include
#include
#include
#include
#include
#include
#include
#include
class TestEdit : public QLineEdit
{
Q_OBJECT
publi
On 9/4/20 2:40 PM, Kyle Edwards wrote:
After some more investigation, I've learned more about the nature of
the problem.
The createEditor() override returns a button which, when clicked,
opens a file dialog (through QFileDialog::getOpenFileName() - this
will be important in a bit). The openin
On 9/4/20 12:06 PM, Kyle Edwards wrote:
Interestingly, the stack trace shows that the widget's destructor is
being called within one of its own methods. Whether it's the same
widget or just the same class but a different instance, I'm not sure
(ASAN's stack trace doesn't print this information.
On 9/3/20 5:49 PM, Giuseppe D'Angelo via Interest wrote:
Do you have a minimal testcase? What does valgrind / ASAN say?
No minimal test case yet. ASAN says the widget's destructor is calling
QObjectPrivate::deleteChildren(), which then says "attempting free on
address which was not malloc()ed
Hi,
AFAIK users of Unix systems can get Qt to use plugins they installed themselves
in a custom/personal location. Is there a way to check programmatically where a
given, loaded plugin lives?
In particular, is there a straightforward way to filter out styles from the
output of `QStyleFactory::
I actually succeeded in implementing a Qt3D widget.
It can be found here: https://github.com/florianblume/qt3d-widget.
Unfortunately, I had to use Qt3D's internal classes so it kind of feels
a bit unstable because it might break with certain Qt versions.
I would have liked to leave all processing
