<![CDATA[mousePressedEvent handler for QTableView]]>I want to handle RMB press events on the viewport and pop a menu when this is done.

When a menu item is chosen, it should apply to all selected rows in the table view.

  1. I think I need to sub-class QTableView to achieve this? Or is there a "neat" way to handle this in the owning widget?

  2. I want to enable some menu items only if the mouse is over a row of the table (rather than a blank area) - how do I do that?

  3. I don't wish to react to RMB on the header, but I think I can just check horizontalHeader()->underMouse() - is that right?

Thanks
David

]]>https://forum.qt.io/topic/139538/mousepressedevent-handler-for-qtableviewRSS for NodeThu, 05 Nov 2026 06:13:12 GMTSat, 24 Sep 2022 10:08:18 GMT60<![CDATA[Reply to mousePressedEvent handler for QTableView on Sat, 24 Sep 2022 10:23:28 GMT]]>@Perdrix

  1. You can usually achieve event handling without subclassing if you go via eventFilter(). But as you add functionality to a QTableView like this it becomes nicer if sub-classed. I would (think ) would be subclassing to override contextMenuEvent().

  2. QTableWidget has an itemAt(). For QTableView what about rowAt(int y) or indexAt(const QPoint &pos)? Check what coordinates the mouse position returns, may have to be mapped to table view, not sure.

  3. Probably yes, or it may come out in the wash from #2.

]]>https://forum.qt.io/post/730027https://forum.qt.io/post/730027Sat, 24 Sep 2022 10:23:28 GMT<![CDATA[Reply to mousePressedEvent handler for QTableView on Wed, 28 Sep 2022 02:33:32 GMT]]>void StackingDlg::on_tableView_customContextMenuRequested(const QPoint& pos)

is what I used - thanks

]]>https://forum.qt.io/post/730432https://forum.qt.io/post/730432Wed, 28 Sep 2022 02:33:32 GMT<![CDATA[Reply to mousePressedEvent handler for QTableView on Tue, 27 Sep 2022 16:24:02 GMT]]>@Perdrix
In addition to being able to subclass and override contextMenuEvent(), there is signal void QWidget::customContextMenuRequested(const QPoint &pos), which does not require subclassing. You choose between event versus signal via setContextMenuPolicy(Qt::ContextMenuPolicy policy) with enum Qt::ContextMenuPolicy.

]]>https://forum.qt.io/post/730377https://forum.qt.io/post/730377Tue, 27 Sep 2022 16:24:02 GMT<![CDATA[Reply to mousePressedEvent handler for QTableView on Tue, 27 Sep 2022 16:15:06 GMT]]>@JonB said in mousePressedEvent handler for QTableView:

contextMenuEvent()

That was what was needed!

Thanks

]]>https://forum.qt.io/post/730375https://forum.qt.io/post/730375Tue, 27 Sep 2022 16:15:06 GMT<![CDATA[Reply to mousePressedEvent handler for QTableView on Sat, 24 Sep 2022 10:23:28 GMT]]>@Perdrix

  1. You can usually achieve event handling without subclassing if you go via eventFilter(). But as you add functionality to a QTableView like this it becomes nicer if sub-classed. I would (think ) would be subclassing to override contextMenuEvent().

  2. QTableWidget has an itemAt(). For QTableView what about rowAt(int y) or indexAt(const QPoint &pos)? Check what coordinates the mouse position returns, may have to be mapped to table view, not sure.

  3. Probably yes, or it may come out in the wash from #2.

]]>https://forum.qt.io/post/730027https://forum.qt.io/post/730027Sat, 24 Sep 2022 10:23:28 GMT