@Ratzz Sorry i can not check your answer as solved answer, Qt forum has a bug about that. I solved my problem, i've already read the topic that you linked here but after you posted it then a read again and i solved my problem thank you, but even so trying to give more explanatory answers is a good way because i like this forum and i want to see answers from another angles, another perspectives. When i get experienced at Qt i want to give good answers too. :) And thank you so much Mr. @dheerendra . I think approach with row is a better way but i was need to a quick way so that stackoverflow link helped me about that.

@philm001 the stylesheet declaration should rather look like this i guess: w->setStyleSheet(QString("QListView::item { background: rgba(255, 0, 0, %1)}").arg(value.toInt())

Well seems that it needs to emit model's layoutChanged() to do what I need. I created new class which inherits QListWidget and there I connected signal to layoutChanged signal of model() object and it worked.

@kishore_hemmady said in QListWidget delete selected item: how can i achieve this by selecting the check Box rather than selecting the list content? for(int i=ui->listWidget->model()->rowCount()-1;i>=0;--i){ if(ui->listWidget->model()->index(i,0).data(Qt::CheckStateRole).toInt()==Qt::Checked) ui->listWidgetMy->model()->removeRow(i); }

@VRonin Oh and you provide a model based solution. Much more elegant :) https://forum.qt.io/topic/72974/link-two-qlistwidget/4

It's good when it's more friendly :)

@WhatIf Can someone show me an example of what other pieces of information it can hold? What type? Any type that's registered for QVariant (declared as a meta-type). Here's what Qt has a data roles, but you can have your own. Kind regards.

I fixed this issue depending on the mentioned snippet here: http://www.qtcentre.org/threads/53580-TapAndHoldGesture-sender-object-name

Hi, Why not use the parameters of currentItemChanged to get the current item ?

Then you should also implement the sizeHint method of your delegate

For that kind of things the combo: QListView QStringListModel QIdentityProxyModel << Customize the icons here would do it in a simpler way. As for items being QObject derived classes, rather not. The various QXXXItem classes must be as lightweight as possible since there can be several thousands of them and QObject has a cost and constraints. Except maybe in a few corner cases there would be no real benefit to have it there for the common usage.