@milan Hi,
You can do it using a delegate and a ToolTip component:

import QtQuick.Controls 2.2 as QC2 ... TableViewColumn { id: titleColumn title: "Title" role: "title" movable: false resizable: false width: tableView.viewport.width - authorColumn.width delegate: QC2.ItemDelegate{ id: lb hoverEnabled: true text: model.title width: parent.width QC2.ToolTip { delay: 250 parent: lb visible: lb.hovered text: "Tooltip text" //put styleData.tooltip here } } }

This code is extracted from the TableView example which I have modified to add the ToolTip.

@mrjj

Thanks I got it to work.

ui->setupUi(this); ui->tableWidget->setColumnCount(2); ui->tableWidget->setRowCount(numberSet.size()); ui->tableWidget->setEditTriggers(QAbstractItemView::NoEditTriggers); QStringList tableHeader = {"Number", "Result"}; ui->tableWidget->setHorizontalHeaderLabels(tableHeader); int rowCounter = 0; for(int i : numberSet) { ui->tableWidget->setItem(rowCounter, 0, new QTableWidgetItem(QString::number(i))); ui->tableWidget->setItem(rowCounter, 1, new QTableWidgetItem(someConversion(i))); rowCounter++; }

@Arthur-Araruna said in Replicate the contents of the current selected item in QTableView:

both column and row indices

All you need to do is replace currentRowChanged with currentIndexChanged

Finaly I have finished my little example!

Previous version have been really buggy in items move. So I have to subclass from QAbstractItemModel. Many thanks to @Patou355 with his solution.

NB I haven't deal with mousePressEvent() yet.

Thank you very much! After your message I totally ran with it (and that example you provided helped a great deal), and got it mostly working. I have a few small problems still that I need to work out, but I think they would be better off in a new thread as they would be off topic here.

Thanks again!

Ok, nice, these three answers (StackView / StackLayout / Loader + Component) were what I was looking for. I tried each one and I think I'll stick with the StackView and the replace method as it's easy to have a fading transition with it. And I've already found a use to improve my code for the Loader so I also thank you for that.
Thx for the help.

thanks. i will try it :)

@VRonin
Can you please provide an example or something to follow? Because I am still a newbie at both Qt and QML.
Sorry for bothering you with my many questions.

Update:
as you can see in the code, I change the state of the delegate through the mouse area in the delegate (it's commented out in the code). I was using it to test the states, now I've noticed another thing; Whenever I collapse the parent Item and then expand it, the previous states are not saved....does this have to do anything with what you mentioned?

In 90% of the cases you can use QStandardItemModel instead of going through the minefield that is subclassing an abstract model.

My advice is just to use that "universal model" instead of a custom one. If you really, really want to customise it as performance of QStandardItemModel is a problem then make sure you run your model through the Model Test (needs just a couple of trivial fixes to work on Qt5) that will tell you if you did everything as you were supposed to or you fell in the countless pitfalls of model subclassing

@6thC did your application consist of a tree and you could apply a delegate to specific items? because that's where I'm stuck now. I am still researching on how to connect QML with C++ and as usual if I figured out a way of applying delegates to specific items based on a logical condition (like your warning and maximum states), I will let you know.

Thanks for your time bro!

@IMAN4K said in change QSortFilterProxyModel behaviour for multiple column filtering:

Answer from stackfverflow : http://stackoverflow.com/questions/39488901/change-qsortfilterproxymodel-behaviour-for-multiple-column-filtering

This answer is the typical example that lead people to say

subclassing QSortFilterProxyModel, which would likely have a very limited reusability

It's bad. the proxy model implementation should not depend on the structure of the underlying data in sourceModel

@NIXIN

class MySortFilterProxyModel : public QSortFilterProxyModel { Q_OBJECT Q_PROPERTY(bool FilterEnabled READ isFilterEnabled WRITE setFilterEnabled ) public: virtual bool filterAcceptsRow(int source_row, const QModelIndex & source_parent) const { if( !m_IsFilterEnabled ) return true; // your filtering code here } bool isFilterEnabled() const { return m_IsFilterEnabled }; void setFilterEnabled( bool enabled ) { if( m_IsFilterEnabled != enabled ) { m_IsFilterEnabled = enabled; this->invalidate(); } } private: bool m_IsFilterEnabled;

@SGaist returning a pointer in the getter and defining the Q_PROPERTY as a pointer to the list worked out fine! Thanks for that!

Like I said, without seeing any code I can't comment on whether the wrong index is being used or something else is going on.

You don't need all of this. Just use the top-most index. Modifying its content will propagate it back to the bottom index.

Hi,

You can try with the QHeaderView::minimumSectionSize property

@tokafr said:

Mydelegate *delegate = new Mydelegate;

hi, i might miss something but why dont you just create another instance?

Mydelegate *delegate2= new Mydelegate;
view2 -> setItemDelegate(delegate2);

Normally a delegate (instance) is not shared between views as its not intended.

I finally managed to get custom colors. I gave my QTreeView an object name to be able to write this in CSS:

m_treeView->setObjectName("MyTreeView"); m_treeView->setStyleSheet("QTreeView#MyTreeView::item {color: none;}");

basically now my model controls text color through Qt::ForegroundRole regardless of the application's CSS.
I feel like it's the wrong place to put theming, but it works for me at the moment.
Well... until we decide to have different themes :-°

@RDiGuida
Ok, so cnamMet would run out of scope and be deleted (when function ended)
but sounds like data.rnames should have been working.
Well if a copy on creation time works for you, its a wrap :)

@mjsurette

That did the trick! I also removed the dataChanged() calls and now the operation executes instantly even with thousands of rows. It also seems there aren't any side effects, apart that I have to call again fetchMore() immediately after select(). I can now move on and implement some other batch operations like this without worrying about speed.

Thank you!

Yeah, according to QComboBox code should work:

QVariant QComboBox::itemData(int index, int role) const { Q_D(const QComboBox); QModelIndex mi = d->model->index(index, d->modelColumn, d->root); return d->model->data(mi, role); }

Will implement this.

Sounds reasonable. Thank you for your help!

@JKSH
Ah, moc assumes first class only. So its simply not supported.
Thats good to know.

@Valerian I did not do d&d yet. In my idea you should register a signal to be emitted whenever you move mouse in the area of new position and call swap function.
Do you feel something like this?

How are you viewing the model?

@Sam2304 The following post may be useful in the resolution of this: How to integrate QSqlTableModel with a tableview defined in qml

Hi,

QAbstractProxyModel comes to mind. You can try assembling both column one on top of the other

Hope it helps

Thanks
problem solved!

You don't actually need to subclass QAbstractItemModel with your current approach. Your QList<SoundObject*> already acts as the model.

In fact, I want to use a QSortFilterProxyModel in C++ to filter what I want to display, and a TableView in QML to enable multiple selection, which is not available in ListView :(
So I had to subclass QAbstractItemModel, and add a custom role that I named "data", which returns the QObject*.

Thank you for everything, I'm going to implement this right away. If I find something useful, I will share it here. And if someone has another idea/vision of how to solve the problem, don't hesitate to share too !

@gardiol Yeah at first it seems to be quite complex (overriding so much stuff etc.. ) but as the data grows and the view becomes more complex the Model/View turns out to be a boon.

Hi and welcome to devnet,

Since you are painting things yourself, you would also need to handle the mouse interaction yourself. Painting a QCheckBox is not the same has having an actual checkbox widget.