Results 1 to 5 of 5

Thread: QT/C++ GUI misconception

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Nov 2015
    Posts
    67

    Default QT/C++ GUI misconception

    I found no answer for this Problem in C++/Qt on the internet:

    command1
    different command
    different command
    different command
    .
    .
    .
    like 1000 different commands
    .
    .
    .
    different command



    No Loop. How does the GUI stay responsive, while this intensive processing??? You cannot write after every command a qWait or a processEvents()

    I only found answers like put a qwait there put a processEvent there and hope it works. Which it clearly does not if there is no loop around it like in my example.

    Is it a misconception of C++/Qt?

    Why should somebody not want responsive GUI? In this case its not possible in c++ is it?

    I think my example is very clear, I hope for simple answers
    Last edited by Ini; 21st March 2016 at 15:53.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Digia, Qt and their respective logos are trademarks of Digia Plc in Finland and/or other countries worldwide.