<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
<div class="moz-cite-prefix">Le 22/10/2015 18:22, Aditya Sharma a
écrit :<br>
</div>
<blockquote
cite="mid:CALHAJW7UQTLzOOQLfdLnB+ffEje7PCQ0wkkw=0HBb4oqzTtAqg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hello,<br>
<br>
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.<br>
<br>
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 can't be
instantiated). Just removing these function calls won't
help either as the classes that derive from these will
also remain an abstract class until these pure virtual
functions are reimplemented in the derived classes.<br>
<br>
So the calls to these specific functions will
automatically turn up as errors during the compilation
process (thus automatically highlighting the need to
take care of the now pure virtual function). Can you
please explain why then is it needed to use pragma in
these cases?<br>
<br>
Regards,<br>
Aroonav.<br>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra">
<div class="gmail_quote"><br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Apart from what Aroonav said, I'd like to add that if
there were these errors, then they would have appeared at
compilation time only. Since each derived class *needs* to
define the function that it's deriving from the abstract
base class.</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
You are right, the problem wasn't this... I figured out after, that
it was because of the Qt::UserRole that changed in Qt5.<br>
<br>
Now I tracked the segmentation fault to
/src/browsers/CollectionTreeItemModelBase.cpp, in <br>
void CollectionTreeItemModelBase::listForLevel(int level,
Collections::QueryMaker * qm, CollectionTreeItem * parent)<br>
<br>
<br>
It appears that removing the last line (QTimer) removes the fault
and that the slot is never triggered. I cannot go further for now.
If you have any ideas.. please tell.<br>
<br>
Cheers!<br>
Olivier<br>
<br>
<blockquote
cite="mid:CALHAJW7UQTLzOOQLfdLnB+ffEje7PCQ0wkkw=0HBb4oqzTtAqg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Regards</div>
<div>Aditya </div>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Amarok-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/amarok-devel">https://mail.kde.org/mailman/listinfo/amarok-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>