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. QThread and pointers

QThread and pointers

Scheduled Pinned Locked Moved Solved General and Desktop
qthreadpointer
12 Posts 3 Posters 5.2k 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.
  • beeckscheB Offline
    beeckscheB Offline
    beecksche
    wrote on last edited by
    #3

    CreateMembers() is called after i moved the workobject to the thread.

    The connection type is set to Qt::AutoConnection.

    Yes, i need them in some other slots again.

    kshegunovK 1 Reply Last reply
    0
    • jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #4

      Then it should be OK.
      The slot is executed in the thread where the object resides, so the objects are created in the same thread.
      Regarding sharing the pointers with other objects: in which thread are those other objects?

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • beeckscheB Offline
        beeckscheB Offline
        beecksche
        wrote on last edited by beecksche
        #5

        The other objects are also created in the createMembers() slot.

        So i can use the shared pointers in the other objects safely, because the objects "live" in the same thread, right?

        1 Reply Last reply
        0
        • beeckscheB beecksche

          CreateMembers() is called after i moved the workobject to the thread.

          The connection type is set to Qt::AutoConnection.

          Yes, i need them in some other slots again.

          kshegunovK Offline
          kshegunovK Offline
          kshegunov
          Moderators
          wrote on last edited by
          #6

          @beecksche said:

          CreateMembers() is called after i moved the workobject to the thread.

          It makes a whole lot of difference how you call it. Is it connected to a signal, do you call it explicitly?

          Read and abide by the Qt Code of Conduct

          1 Reply Last reply
          0
          • beeckscheB Offline
            beeckscheB Offline
            beecksche
            wrote on last edited by
            #7

            Sorry, i haven't told you yet. It's connected to a signal!

            kshegunovK 1 Reply Last reply
            0
            • beeckscheB beecksche

              Sorry, i haven't told you yet. It's connected to a signal!

              kshegunovK Offline
              kshegunovK Offline
              kshegunov
              Moderators
              wrote on last edited by
              #8

              @beecksche
              Then it's perfectly fine.

              Read and abide by the Qt Code of Conduct

              1 Reply Last reply
              0
              • beeckscheB Offline
                beeckscheB Offline
                beecksche
                wrote on last edited by
                #9

                Perfect, thanks a lot!

                kshegunovK 1 Reply Last reply
                0
                • beeckscheB beecksche

                  Perfect, thanks a lot!

                  kshegunovK Offline
                  kshegunovK Offline
                  kshegunov
                  Moderators
                  wrote on last edited by
                  #10

                  @beecksche
                  No worries.
                  Although,QScopedPointer might be appropriate here (looking at your code), you may want to check it out.

                  Read and abide by the Qt Code of Conduct

                  1 Reply Last reply
                  0
                  • beeckscheB Offline
                    beeckscheB Offline
                    beecksche
                    wrote on last edited by beecksche
                    #11

                    The advatage of a QScopedPointer is that you don't have to care about the destruction of the object, right?
                    The object will be destroyed when the pointer is out of scope?

                    kshegunovK 1 Reply Last reply
                    0
                    • beeckscheB beecksche

                      The advatage of a QScopedPointer is that you don't have to care about the destruction of the object, right?
                      The object will be destroyed when the pointer is out of scope?

                      kshegunovK Offline
                      kshegunovK Offline
                      kshegunov
                      Moderators
                      wrote on last edited by
                      #12

                      @beecksche said:

                      The advatage of a QScopedPointer is that you don't have to care about the destruction of the object, right?

                      Yes. It's a thin wrapper around the raw pointer and will delete the held reference when it goes out of scope. The idea is to use the stack based QScopedPointer object to manage the heap-allocated object it's referencing.

                      Kind regards.

                      Read and abide by the Qt Code of Conduct

                      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