Basic Qt5 UI with button












3














I have the following Qt class:
mainwindow.h



class MainWindow : public QWidget {
Q_OBJECT
QPushButton* m_button;
public:
explicit MainWindow();
};


mainwindow.cpp



MainWindow::MainWindow() {
auto main_layout = new QHBoxLayout;
m_button = new QPushButton("Press me");
main_layout->addWidget(m_button);
setLayout(main_layout);
connect(m_button, &QPushButton::pressed, [this] {
m_button->setText("Presse me again");
});
}


It features a button which once pressed will change its text to "Press me again". I use a lambda function and I am capturing by copy this to access the button inside the lambda.



As the QPushButton is allocated on the heap, I think that making it a class member is an unnecessary step. My question: Are there any drawbacks if I instead use it as a local pointer which I would capture by copy in the connect lambda ? It would look like this:



mainwindow.h



class MainWindow : public QWidget {
Q_OBJECT
public:
explicit MainWindow();
};


mainwindow.cpp



MainWindow::MainWindow() {
auto main_layout = new QHBoxLayout;
auto button = new QPushButton("Press me");
main_layout->addWidget(button);
setLayout(main_layout);
connect(button, &QPushButton::pressed, [button] { // I am copying the button's address here
button->setText("Presse me again");
});
}


One thing to note: Qt manages the destruction of all Qt classes automatically, so no need to call the button's destructor later if I understood correctly this conversation.










share|improve this question





























    3














    I have the following Qt class:
    mainwindow.h



    class MainWindow : public QWidget {
    Q_OBJECT
    QPushButton* m_button;
    public:
    explicit MainWindow();
    };


    mainwindow.cpp



    MainWindow::MainWindow() {
    auto main_layout = new QHBoxLayout;
    m_button = new QPushButton("Press me");
    main_layout->addWidget(m_button);
    setLayout(main_layout);
    connect(m_button, &QPushButton::pressed, [this] {
    m_button->setText("Presse me again");
    });
    }


    It features a button which once pressed will change its text to "Press me again". I use a lambda function and I am capturing by copy this to access the button inside the lambda.



    As the QPushButton is allocated on the heap, I think that making it a class member is an unnecessary step. My question: Are there any drawbacks if I instead use it as a local pointer which I would capture by copy in the connect lambda ? It would look like this:



    mainwindow.h



    class MainWindow : public QWidget {
    Q_OBJECT
    public:
    explicit MainWindow();
    };


    mainwindow.cpp



    MainWindow::MainWindow() {
    auto main_layout = new QHBoxLayout;
    auto button = new QPushButton("Press me");
    main_layout->addWidget(button);
    setLayout(main_layout);
    connect(button, &QPushButton::pressed, [button] { // I am copying the button's address here
    button->setText("Presse me again");
    });
    }


    One thing to note: Qt manages the destruction of all Qt classes automatically, so no need to call the button's destructor later if I understood correctly this conversation.










    share|improve this question



























      3












      3








      3







      I have the following Qt class:
      mainwindow.h



      class MainWindow : public QWidget {
      Q_OBJECT
      QPushButton* m_button;
      public:
      explicit MainWindow();
      };


      mainwindow.cpp



      MainWindow::MainWindow() {
      auto main_layout = new QHBoxLayout;
      m_button = new QPushButton("Press me");
      main_layout->addWidget(m_button);
      setLayout(main_layout);
      connect(m_button, &QPushButton::pressed, [this] {
      m_button->setText("Presse me again");
      });
      }


      It features a button which once pressed will change its text to "Press me again". I use a lambda function and I am capturing by copy this to access the button inside the lambda.



      As the QPushButton is allocated on the heap, I think that making it a class member is an unnecessary step. My question: Are there any drawbacks if I instead use it as a local pointer which I would capture by copy in the connect lambda ? It would look like this:



      mainwindow.h



      class MainWindow : public QWidget {
      Q_OBJECT
      public:
      explicit MainWindow();
      };


      mainwindow.cpp



      MainWindow::MainWindow() {
      auto main_layout = new QHBoxLayout;
      auto button = new QPushButton("Press me");
      main_layout->addWidget(button);
      setLayout(main_layout);
      connect(button, &QPushButton::pressed, [button] { // I am copying the button's address here
      button->setText("Presse me again");
      });
      }


      One thing to note: Qt manages the destruction of all Qt classes automatically, so no need to call the button's destructor later if I understood correctly this conversation.










      share|improve this question















      I have the following Qt class:
      mainwindow.h



      class MainWindow : public QWidget {
      Q_OBJECT
      QPushButton* m_button;
      public:
      explicit MainWindow();
      };


      mainwindow.cpp



      MainWindow::MainWindow() {
      auto main_layout = new QHBoxLayout;
      m_button = new QPushButton("Press me");
      main_layout->addWidget(m_button);
      setLayout(main_layout);
      connect(m_button, &QPushButton::pressed, [this] {
      m_button->setText("Presse me again");
      });
      }


      It features a button which once pressed will change its text to "Press me again". I use a lambda function and I am capturing by copy this to access the button inside the lambda.



      As the QPushButton is allocated on the heap, I think that making it a class member is an unnecessary step. My question: Are there any drawbacks if I instead use it as a local pointer which I would capture by copy in the connect lambda ? It would look like this:



      mainwindow.h



      class MainWindow : public QWidget {
      Q_OBJECT
      public:
      explicit MainWindow();
      };


      mainwindow.cpp



      MainWindow::MainWindow() {
      auto main_layout = new QHBoxLayout;
      auto button = new QPushButton("Press me");
      main_layout->addWidget(button);
      setLayout(main_layout);
      connect(button, &QPushButton::pressed, [button] { // I am copying the button's address here
      button->setText("Presse me again");
      });
      }


      One thing to note: Qt manages the destruction of all Qt classes automatically, so no need to call the button's destructor later if I understood correctly this conversation.







      c++ comparative-review pointers heap qt






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 days ago









      Graham

      1,126115




      1,126115










      asked 2 days ago









      LeogoutLeogout

      1467




      1467






















          0






          active

          oldest

          votes











          Your Answer





          StackExchange.ifUsing("editor", function () {
          return StackExchange.using("mathjaxEditing", function () {
          StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
          StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
          });
          });
          }, "mathjax-editing");

          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "196"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f211026%2fbasic-qt5-ui-with-button%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Code Review Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          Use MathJax to format equations. MathJax reference.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f211026%2fbasic-qt5-ui-with-button%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Terni

          A new problem with tex4ht and tikz

          Sun Ra