Hi,
once again I was wrong.
The issue is triggered according to what you comment in the
listForLevel() function (the one I was talking about sooner)... But what
exactly and why? I'm still searching...
Olivier
Le 22/10/2015 20:03, Olivier Churlaud a écrit :
Hi,
Le 22/10/2015 18:22, Aditya S
Hi,
Le 22/10/2015 18:22, Aditya Sharma a écrit :
Hello,
Sorry for not being able to get back to you on IRC. I have been
busy with another project of mine at my university for quite some
time now.
If a method was virtual before and is pure virtual now then one
can't cal
> Hello,
>
> Sorry for not being able to get back to you on IRC. I have been busy with
> another project of mine at my university for quite some time now.
>
> If a method was virtual before and is pure virtual now then one can't call
> that function as the method is of an abstract class now in Qt5
Hello,
Sorry for not being able to get back to you on IRC. I have been busy with
another project of mine at my university for quite some time now.
If a method was virtual before and is pure virtual now then one can't call
that function as the method is of an abstract class now in Qt5 (and hence
c
Hi,
I found why we get so many nasty segfault...
Several methods of Qt4 (which were virtual) are now (with Qt5) pure
virtual, meaning that they are defined like:
virtual void myfunction( ...args...) = 0 ;
Therefore calling them produces a segfault...
IMO, we should first comment them
