Okay, after writing a small example I think I'm grasping how
model->proxy->delegate->view all operate together. Hoewver, I have
found a single caveat that I haven't been able to figure out:
For my QSortFilterProxyModel, I'm using mapToSource( const QModelIndex&
) to magically get the "real" index
On 06/01/2012 03:01 PM, Jordi Pujol wrote:
> El dv 01 de 06 de 2012 a les 14:15 +0900, en/na Paul England va
> escriure:
>> Hi
>>
>> I wrote this really long email, and learned a lot about the problem in
>> doing so. So, I guess it was time well spent. Still frust
Hi
I wrote this really long email, and learned a lot about the problem in
doing so. So, I guess it was time well spent. Still frustrated.
Here's the summed up problem:
I have a QAbstrctTabelModel, QSortFilterProxyModel, QItemDelegate, and a
QTableView (all subclassed). As you'd expect, the QS
Hi. Thanks for the reply.
later.
The proper answer to this is that you need to run this through a
profiler. You know, premature optimization...
If your code runs on Linux, you should take a look at KCacheGrinder.
Indeed, and this has been mentioned by someone else on the team... right
now,
Hi
I've got an old legacy application that I started in Qt3 and have since
ported to Qt4. It uses a subclassed QTableWidget. I'm using about 8
columns. Data is added at various rates, but I would say by the end of
the day, it could have several thousand rows. To boot, I'm actually
kicking
