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. Wierd behaviour after call to QWidget::winId().
Forum Updated to NodeBB v4.3 + New Features

Wierd behaviour after call to QWidget::winId().

Scheduled Pinned Locked Moved Unsolved General and Desktop
3 Posts 2 Posters 349 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.
  • T Offline
    T Offline
    Tahir Majeed
    wrote on last edited by Tahir Majeed
    #1

    Hi,

    I have a QFrame object. I cast it to QWidget and then call the windId() method. After the call to winId() the mouse clicks on buttons and touch events stop working. The same behavior is observed with effectiveWinId().

    When I use internalWinId() and effectiveWinId(), things work fine. I do not loose the mouse clicks and touch events on buttons.

    There is a very old bug which still appears unresolved.
    https://bugreports.qt.io/browse/QTBUG-30181

    I think I have run into the same problem.

    I am using Qt 5.15.8 - GCC 9.4.0 64 bit - Ubuntu 20.04.

    Can you please help me, whether its a bug or am I doing something wrong?

    Is it ok to use internalWinId() instead of winId() or should I take care of something?

    Thank you,
    Tahir

    Christian EhrlicherC 1 Reply Last reply
    0
    • T Tahir Majeed

      Hi,

      I have a QFrame object. I cast it to QWidget and then call the windId() method. After the call to winId() the mouse clicks on buttons and touch events stop working. The same behavior is observed with effectiveWinId().

      When I use internalWinId() and effectiveWinId(), things work fine. I do not loose the mouse clicks and touch events on buttons.

      There is a very old bug which still appears unresolved.
      https://bugreports.qt.io/browse/QTBUG-30181

      I think I have run into the same problem.

      I am using Qt 5.15.8 - GCC 9.4.0 64 bit - Ubuntu 20.04.

      Can you please help me, whether its a bug or am I doing something wrong?

      Is it ok to use internalWinId() instead of winId() or should I take care of something?

      Thank you,
      Tahir

      Christian EhrlicherC Offline
      Christian EhrlicherC Offline
      Christian Ehrlicher
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @Tahir-Majeed said in Wierd behaviour after call to QWidget::winId().:

      Can you please help me, whether its a bug or am I doing something wrong?

      Without even a single line of code?
      Please provide a minimal compilable example.

      Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
      Visit the Qt Academy at https://academy.qt.io/catalog

      T 1 Reply Last reply
      0
      • Christian EhrlicherC Christian Ehrlicher

        @Tahir-Majeed said in Wierd behaviour after call to QWidget::winId().:

        Can you please help me, whether its a bug or am I doing something wrong?

        Without even a single line of code?
        Please provide a minimal compilable example.

        T Offline
        T Offline
        Tahir Majeed
        wrote on last edited by
        #3

        @Christian-Ehrlicher Thank you, I will create a Minimal Compilable example that can reproduce the bug. Currently, I have a proprietary code that I can not share.

        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