How to be notified when a row is hovered in a QFormLayout?



  • I have a QFormLayout where the left widgets are QLabels and the right widgets are of various types. I want to get notified when the mouse enters any part of a form-row, so I can display an explanation of that row in my statusbar.

    Currently I have a QLabel subclass called HoverableLabel which exposes "mouseEntered" and "mouseLeft" signals (emitted in my reimplementations of enterEvent and leaveEvent). This works, but:

    • The margins between the rows don't trigger the signals
    • The space on the left of the (right-aligned) labels doesn't trigger the signal
    • The widgets on the right don't trigger the signal because I haven't bothered to subclass all of them
    • What's the Qt-blessed approach to this kind of problem?

    Some things I can think of:

    • Make the formlayout's parent a widget that filters all mousemove events (mouse tracking?) and checks if the mouse has entered some row.
    • Change the formlayout into a QVBoxLayout, and make the rows into some custom widget like FormRowWidget which handles both hover events and the form-alignment stuff.

    Neither is very nice.



  • As I think the best variant is your second variant. Also you can just make QVBoxLayout of QWidgets and set to each of them FormLayout with one row. This way you will not needed to handle alignment.



  • I would still need to handle alignment. By alignment I don't mean whether the label is left or right aligned! What I mean is the necessity to have the fields line up with each other vertically (similarly to a QGridLayout).



  • Oh yeah, haven't took it in case. Then I think that you can create additional mediator-class for align this widgets identically through this class.



  • Another solution could be to use QTreeWidget/QTableWidget, maybe?



  • [quote author="mario" date="1285568589"]Another solution could be to use QTreeWidget/QTableWidget, maybe?[/quote]
    Yeah, maybe. Delegates will help author.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.