Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for Python
  4. Using Signals in QGraphicsItem
QtWS25 Last Chance

Using Signals in QGraphicsItem

Scheduled Pinned Locked Moved Solved Qt for Python
25 Posts 5 Posters 1.1k Views
  • 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.
  • J JonB
    25 Feb 2025, 09:24

    @adrien-lsh
    Since you seem to have provided a nice, standalone, complete example I can copy and paste --- unlike so many other people --- I will give it a play now....

    J Offline
    J Offline
    JonB
    wrote on 25 Feb 2025, 09:31 last edited by
    #16

    @JonB
    Your code above, copied and pasted, works fine for me. Ubuntu 24.04, Qt 6.4.2, PySide6. Or at least I get an open window with a line in it. Could you be very specific about what you do to make it "crash"?

    A 1 Reply Last reply 25 Feb 2025, 09:32
    0
    • J JonB
      25 Feb 2025, 09:31

      @JonB
      Your code above, copied and pasted, works fine for me. Ubuntu 24.04, Qt 6.4.2, PySide6. Or at least I get an open window with a line in it. Could you be very specific about what you do to make it "crash"?

      A Offline
      A Offline
      adrien-lsh
      wrote on 25 Feb 2025, 09:32 last edited by
      #17

      @JonB
      Try to move the line.

      J 1 Reply Last reply 25 Feb 2025, 09:35
      0
      • A adrien-lsh
        25 Feb 2025, 09:32

        @JonB
        Try to move the line.

        J Offline
        J Offline
        JonB
        wrote on 25 Feb 2025, 09:35 last edited by
        #18

        @adrien-lsh
        Yeah, that's easier said than done! It's so thin, and I can't tell when I have actually grabbed it or not! Anyway I have reproed now, it does a SIGSEGV from

        0x00007ffff711fc14 in PySide::SignalManager::emitSignal(QObject*, char const*, _object*) ()
           from /home/jon/.venv/pyside6/lib/python3.12/site-packages/PySide6/libpyside6.abi3.so.6.7
        (gdb) bt
        #0  0x00007ffff711fc14 in PySide::SignalManager::emitSignal(QObject*, char const*, _object*) ()
            at /home/jon/.venv/pyside6/lib/python3.12/site-packages/PySide6/libpyside6.abi3.so.6.7
        

        Looking into that now...

        A 1 Reply Last reply 25 Feb 2025, 09:36
        0
        • J JonB
          25 Feb 2025, 09:35

          @adrien-lsh
          Yeah, that's easier said than done! It's so thin, and I can't tell when I have actually grabbed it or not! Anyway I have reproed now, it does a SIGSEGV from

          0x00007ffff711fc14 in PySide::SignalManager::emitSignal(QObject*, char const*, _object*) ()
             from /home/jon/.venv/pyside6/lib/python3.12/site-packages/PySide6/libpyside6.abi3.so.6.7
          (gdb) bt
          #0  0x00007ffff711fc14 in PySide::SignalManager::emitSignal(QObject*, char const*, _object*) ()
              at /home/jon/.venv/pyside6/lib/python3.12/site-packages/PySide6/libpyside6.abi3.so.6.7
          

          Looking into that now...

          A Offline
          A Offline
          adrien-lsh
          wrote on 25 Feb 2025, 09:36 last edited by
          #19

          @JonB
          Yeah I should've set a bigger width ^^. Thank you.

          J 1 Reply Last reply 25 Feb 2025, 09:50
          0
          • A adrien-lsh
            25 Feb 2025, 09:36

            @JonB
            Yeah I should've set a bigger width ^^. Thank you.

            J Offline
            J Offline
            JonB
            wrote on 25 Feb 2025, 09:50 last edited by JonB
            #20

            @adrien-lsh
            I think it is to do with the initialisation, requiring both inherited classes to be initialised. You were only doing so for the QGraphicsLineItem, not initialising the QObject. I find the following does work without crashing:

            class CroppingLine(QObject, QGraphicsLineItem):
                moved = Signal(object, QPointF)
            
                def __init__(self, x1: float, y1: float, x2: float, y2: float):
                    #super(QGraphicsLineItem, self).__init__(x1, y1, x2, y2)
                    QObject.__init__(self)
                    QGraphicsLineItem.__init__(self, x1, y1, x2, y2)
            

            There may be other ways of doing this with super() and/or not swapping the inheritance order, I just know this works fine.

            A 1 Reply Last reply 25 Feb 2025, 10:03
            1
            • A adrien-lsh has marked this topic as solved on 25 Feb 2025, 10:03
            • J JonB
              25 Feb 2025, 09:50

              @adrien-lsh
              I think it is to do with the initialisation, requiring both inherited classes to be initialised. You were only doing so for the QGraphicsLineItem, not initialising the QObject. I find the following does work without crashing:

              class CroppingLine(QObject, QGraphicsLineItem):
                  moved = Signal(object, QPointF)
              
                  def __init__(self, x1: float, y1: float, x2: float, y2: float):
                      #super(QGraphicsLineItem, self).__init__(x1, y1, x2, y2)
                      QObject.__init__(self)
                      QGraphicsLineItem.__init__(self, x1, y1, x2, y2)
              

              There may be other ways of doing this with super() and/or not swapping the inheritance order, I just know this works fine.

              A Offline
              A Offline
              adrien-lsh
              wrote on 25 Feb 2025, 10:03 last edited by
              #21

              @JonB
              Of course ! It never initialized the QObject so signals would never work.
              Thank you for your help !

              1 Reply Last reply
              0
              • S Offline
                S Offline
                SGaist
                Lifetime Qt Champion
                wrote on 25 Feb 2025, 10:23 last edited by SGaist
                #22

                Hi,

                It's Python3, remove the class from your super calls. This should allow Python to do proper initialisation of the chain of classes (though sometimes it might fail for complex cases).

                [Edit: we are in such a complex case]

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                J 1 Reply Last reply 25 Feb 2025, 10:27
                0
                • S SGaist
                  25 Feb 2025, 10:23

                  Hi,

                  It's Python3, remove the class from your super calls. This should allow Python to do proper initialisation of the chain of classes (though sometimes it might fail for complex cases).

                  [Edit: we are in such a complex case]

                  J Offline
                  J Offline
                  JonB
                  wrote on 25 Feb 2025, 10:27 last edited by JonB
                  #23

                  @SGaist
                  But the OP started with just

                  super().__init__(x1, y1, x2, y2)
                  

                  and, for whatever reason, that segments (later, on signal emit) because the QObject part has not been initialized, apparently. That is why I tried splitting it into two separate explicit initializations, which makes it work. So what exactly are you proposing?

                  S 1 Reply Last reply 25 Feb 2025, 11:18
                  0
                  • J JonB
                    25 Feb 2025, 10:27

                    @SGaist
                    But the OP started with just

                    super().__init__(x1, y1, x2, y2)
                    

                    and, for whatever reason, that segments (later, on signal emit) because the QObject part has not been initialized, apparently. That is why I tried splitting it into two separate explicit initializations, which makes it work. So what exactly are you proposing?

                    S Offline
                    S Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on 25 Feb 2025, 11:18 last edited by SGaist
                    #24

                    @JonB I misread the code !

                    We are in the territory where your solution (using __init__) is the way to go. Multiple inheritance in Python is quite tricky...

                    QObject expects an optional parent parameter which is not given here but it's not expecting the parameters for the QGraphicsLineItem constructor hence the failure. You can try to use the kwargs trick however it won't work either as it's not part of any of the method signature and thus can't work either.

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    1 Reply Last reply
                    0
                    • N Offline
                      N Offline
                      Nlight
                      wrote on 25 Feb 2025, 20:02 last edited by Nlight
                      #25
                      This post is deleted!
                      1 Reply Last reply
                      0

                      25/25

                      25 Feb 2025, 20:02

                      • Login

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