you could try to create a “color edit fields”, which has a color field and a button (like a combo box) and open the dialog from there. It could perhaps work, esopecially, as QComboBox also works.

On our application we have similar needs (dialog to edit an item index). We do it this way:

• in the delegate check in createEditor(), if a dialog is needed for editing. If yes, return a null pointer (that restrains the view from editing the index); if no return the base class’ implementation
• connect signal QAbstractItemView::doubleClicked() [doc.qt.nokia.com] (or some overload signal from the specialized item views) to a slot
• in that slot, check if the dialog is needed, if yes create it, show it with exec() and set the value if it returns with “OK”

This way you still have inline editing for text fields, and create a dialog for the complex editing.

Hi!

Volker, I implemented this idea.

I created model’s class

and I implemented showDialogIfNeed and overrode function flags to disable editable of color column

It works fine but function showDialogIfNeed places in Model. It is mix gui and logic.

Are there more correct solutions without the mix?

You can handle everything in the view class or another class that has access to the view. Just show the dialog in the on_penTableView_doubleClicked() slot and set the retrieved data in the model with setData().