Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Mouse events sent to wrong widget (QTableView as QSplitter child)
Forum Updated to NodeBB v4.3 + New Features

Mouse events sent to wrong widget (QTableView as QSplitter child)

Scheduled Pinned Locked Moved General and Desktop
5 Posts 3 Posters 2.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    GregVV
    wrote on last edited by
    #1

    Hi,

    I've created a QSplitter with a QTableView and another widget as its children (table view is the top widget, the other widget is the bottom widget); the splitter is used in a QDialog.

    When the dialog is initially shown there is no selection in the table (which shows a vertical scroll bar as there are more rows than can be shown in the dialog).

    If I now select the first item and then try to resize the space allotted to the table view, the table view gets the mouse events instead of the splitter handle.

    Has anyone else encountered this problem and is there a workaround? (I'm using Qt 4.7 on OS X Snow Leopard)

    1 Reply Last reply
    0
    • G Offline
      G Offline
      goetz
      wrote on last edited by
      #2

      I did not spot this so far.

      If you can create a small, complete test case that demonstrates the behavior, I'd be happy do have a look at it.

      http://www.catb.org/~esr/faqs/smart-questions.html

      1 Reply Last reply
      0
      • G Offline
        G Offline
        GregVV
        wrote on last edited by
        #3

        Although I can systematically reproduce the problem in my application, I didn't have any luck yet reproducing the behavior in a small test class. As soon as I do I'll post the test code here.

        1 Reply Last reply
        0
        • A Offline
          A Offline
          andre
          wrote on last edited by
          #4

          That in itself points towards a problem in your application, instead of in Qt. Are you messing about with eventfilters or something like that per chance?

          1 Reply Last reply
          0
          • G Offline
            G Offline
            GregVV
            wrote on last edited by
            #5

            I'm closing in on the cause of the problem: at the moment it looks like there may be some interference from some network activity (we react to the selection change by making a SOAP call using IPWorks). Removing the SOAP call also gets rid of the problem (unfortunately also of the functionality of the dialog) which would explain why I can't reproduce it in a simple tester and nobody else has encountered this.

            I'm afraid I'll have some long hours of debugging in front of me...

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved