separate QTableWidget into a QTableView and a QStandardItemModel
add a QSortFilterProxyModel as the model of QTableView and set the QStandardItemModel as the QSortFilterProxyModel's sourceModel
call QSortFilterProxyModel::setFilterWildcard or QSortFilterProxyModel::setFilterRegExp to perform the searching
@kylecorver Can you post the complete program? The original isn't a a valid Qml document, leading to guessing about which errors will or will not occur. The OS and Qt version used might also be relevant.
Hi when you add "xxxx" to a qlistwidget
you are adding a QListWidgetItem.
While you can subclass QListWidgetItem and make your own
that has signals, it would not do you so much good as
it would never never emit such signal unless you also made it do
so when something happen to it. (overriding some of its functions)
So It all depends what you are trying to do.
If you just want to know its no 1,2,3 etc, even if moved
you can insert that info into the QListWidgetItem using the
void QListWidgetItem::setData(int role, const QVariant & value)
QListWidgetItem * item=new QListWidgetItem("item1") ;
item->setData(Qt::UserRole, 1); // or 2 for item 2 etc
I do not understand last question. I do not see any problem with mapping which rely on the item bounding rectangle.
You can have an infinite number of visually the same graphics items if you use different combination of position and bounding box parameters.
For example if you create QGraphicsEllipseItem using following rectangle/position pairs you will get the same result on the screen?
QRectF rect1( 0, 0, 1., 2 );
QRectF rect1( 10,20, 1., 2 );
yes, you're right. But in my case this is unfortunately not possible. What I am doing is developing a Toolkit with a bunch of Controls for displaying data. These controls are not used by me (even not used by really developers) but used by people who are configuring the UI pages via drag and drop in the Quick Designer. This is why the logic should be encapsulated within the control...