Actually, since the base class already has a virtual destructor you can just remove the destructor of your derived altogether

@sm4ll-3gg said in How to resize QListView row to index widget size:

what I should read to better understand Model / View / Delegate programming?

Basically everything I know comes from Advanced Qt Prgramming: Creating Great Software with C++ and Qt4

It is normal to set new delegate for each item if I need to show heterogeneous data in list?

No. What I would do is create a QStackedWidget with the possible combinations, use that as base and display the correct page based on the data in the index

I've found a satisfactory solution. I found out the horizontalScrollBar->maximum changes with each successive paint event. I can calculate what the maximum should be and then determine which is the last paint event.

@the_
no it is Qt::ScrollBarAsNeeded.but scrolbar appears correctly after I resize the main widget even with 1 px.

Technically you have a two-level tree.

You can still use that example as a base. In place of their custom TreeViewItem you have your Parent and Child.

Those the abstract model would be a wrapper around your Parent/Child combo.

Can you check with a more recent version of Qt ?

I can't reproduce your problem, I don't know what i should be. But if I remove the showPopup method it shows the combobox at the right place for OS X.

I apologise for the delay in response. The question was to make sure that the combobox always pops up in a given direction or position.

@hskoglund I already have an underlying data store and I'm using a subclass of QAbstractTableModel to bridge it into a Qt GUI.

Making two in-memory copies of that data store and then jerry-rigging View-like synchronization between the actual data and two widget-specific data stores (plus all the requisite automated testing to make sure it works reliably) seems like the exact opposite of what I want.

@Joel-Bodenmann

Sometimes it's hard to track down inherited members from the base page of the class. When you're in doubt you can go to the "List of all members, including inherited members" page. ;)

@raven-worx
Thanks bro,
very helpfull.

@SolaVitae
Do you have any additional stylesheet set for a widget in the parent hierarchy?
Because the posted stylesheet of yours shouldn't result in this effect.

@_compiler said:

thanks.

Since you are interfacing a SQL database, why not make use of the dedicate models ? That would simplify things.

QTBUG-52230 should rather be followed.

Wow. These are some useful references. Thanks a lot. I mark this thread solved.

Hi and welcome
not directly an answer, but have you looked at the example ?
http://doc.qt.io/qt-5/qtwidgets-dialogs-findfiles-example.html

there is also QFileSystemModel
http://doc.qt.io/qt-5/qfilesystemmodel.html#details
to be used with views.

also, just to be sure u saw it
http://doc.qt.io/qt-5/model-view-programming.html

Good intro on how it fits together.

Viele danke Herr Sam :)

First of all, as mentioned in the docs, Qt::TextColorRole is obsolete and you should not use it. Use Qt::ForegroundRole instead.
Second, as mentioned by @alex_malyu, it depends on the model whether or not it implements that. QStandardItemModel for example will, but your custom model might not.
So the question is what is your model class.

Did you try to redefine wheelEvent of your list view?

I think I take your meaning. As I geared up to subclass QAbstractItemView, it also became evident how niche my new class would be. Based on this, I decided to take your advice of composing a custom widget.

If anyone should want to subclass QAbstractItemView, this is a good article to get you started.