QTableView/QStyledItemDelegate: Mark an *entire* row hovered over with the mouse

[SGaist]

Hi,

Your solution doesn't sound bad, you might however simplify things by creating a copy of the options and update state with QStyle::State_MouseOver, you can then let the base implementation do the painting

[thEClaw]

I need full control over the paint-function anyway, and I can't completely follow your thoughts. Are you talking about a fake MouseOver state I should trigger? The ItemDelegate only ever draws a single cell, as far as I know. And I wasn't able to manipulate the calling of that drawing, since it is done in non-reimplementable QTableView-functions.

The solution wasn't too good, by the way. I had to make some small adjustments to it. It's still roughly the same, though.

[SGaist]

No, I was thinking: just add the QStyle::State_MouseOver flag to the option.state flags when needed.

[thEClaw]

Well, since I am doing all the drawing by hand, and I still need to draw the MouseOver-state anyway (the item delegate doesn't have an option for that, right?), I am not sure if I would gain anything by that.

[SGaist]

Aren't you just painting a focus rectangle over the each item of the row ?

[thEClaw]

You see what I'm painting in the code above (last block). Technically it doesn't have anything to do with focus. Would the item delegate be able to highlight the/a focused cell via its standard implementation of paint()?

[SGaist]

Sorry, my bad, I've mixed hovered and selected. But since you are painting the hovered state like the selected, the technic I proposed earlier (using an updated copy of the option) is still usable, you would only need to add the QStyle::State_Selected and then call QAbstractItemDelegate::paint with this new option. It should handle the drawing for you properly

[thEClaw]

But at which point am I supposed to set that option? "Copying" it would be meaningless inside the item delegates paint() function, since that one only draws a single cell, and I have to explicitly check for the hovered-state anyway.

If you are talking about manipulating the option before calling QStyledItemDelegate::paint() in my custom implementation, that's not possible. As I said: I completely rewrote that function, without any calls to the base class being made.

[SGaist]

Ok, it wasn't clear that all the painting was custom. Then no need for my idea.

I just thought about something that may be of interest, what about QRubberBand ?

[thEClaw]

That sounds interesting indeed. I have never used a QRubberBand before - what would happen to the text in the tableview? Would it still be readable?

When doing this in the item delegate, I can paint the background of the text before writing the text, so the hover-marking is cleanly realized (but it still has some minor flaws). An overlayed widget might wash out the text.

[SGaist]

IIRC, the QRubberBand is translucent so you would only have to handle its size and position. You could do it directly in a custom view and wouldn't need your special delegate