Qt-jambi-interest Archive, September 2006
Re: QCheckListItem
Message 1 in thread
>
>> ?? Anyway the problem with overriding the wrong method is best solved
>> by making the correct methods abstract, so the coder gets immediate
>> feedbacks
>
> That is already fixed for the upcoming tech preview.
>
OK, very good, but that raised another tricky problem: What to return from
QAbstractTableModel.data(QModelIndex index, int role) when you only
want to modify Qt.DisplayMode behaviour? Just return
QAbstractTableModel.data(QModelIndex index) for the rest of the cases?
PS: I was a bit disappointed that you didn't find place for the JavaDoc
stuff
in tp2 :'( . Next release maybe? And it wasn't any note about fixing
the problem with QObject.moveToThread(QCoreApplication.instance().thread());
not working...
Regards
Helge F.
Message 2 in thread
Helge Fredriksen wrote:
>
>>
>>> ?? Anyway the problem with overriding the wrong method is best solved
>>> by making the correct methods abstract, so the coder gets immediate
>>> feedbacks
>>
>>
>> That is already fixed for the upcoming tech preview.
>>
>
> OK, very good, but that raised another tricky problem: What to return from
> QAbstractTableModel.data(QModelIndex index, int role) when you only
> want to modify Qt.DisplayMode behaviour? Just return
> QAbstractTableModel.data(QModelIndex index) for the rest of the cases?
You can just return super.data() (if available) or null (e.g. an invalid
QVariant) in those cases.
> PS: I was a bit disappointed that you didn't find place for the
> JavaDoc stuff in tp2 :'( . Next release maybe?
As you can see, we have it on our todo list:
http://www.trolltech.com/developer/task-tracker/index_html?method=entry&id=124409
We just don't know exactly when we'll do it yet ;-)
> And it wasn't any note about fixing the problem with
> QObject.moveToThread(QCoreApplication.instance().thread()); not
> working...
Indeed. This turned out to be a bug in the example ;-)
Complete working code for Invokable is attached. This will be most
likely be part of the API in tp3.
-
Gunnar
Message 3 in thread
Gunnar Sletta wrote:
>
> Indeed. This turned out to be a bug in the example ;-)
>
> Complete working code for Invokable is attached. This will be most
> likely be part of the API in tp3.
>
Hmm, what attachment?
Btw. I'm getting these when I run System.exit(0).
QFont: It is not safe to use text and fonts outside the gui thread
QFont: It is not safe to use text and fonts outside the gui thread
QFont: It is not safe to use text and fonts outside the gui thread
QObject::killTimers: timers cannot be stopped from another thread
Why? I have already returned from QApplication.exec() and would
then think that Jambi was finishied doing it's stuff and that it
should be safe to call System.exit() to make all threads exit. I've
checked my code, and there isn't any Jambi calls beeing made in
leftover threads after QApplication is finished.
Helge
