General and Desktop

Hi, To ensure they are pushed to the left, add a stretch after the last button.

What are you going to use for your AI related activities ?

Hi and welcome to devnet, You are using a relative path so your application will not find the file as it is not located in the same folder. On an unrelated not, please give your thread a meaningful title and put the actual text of your enquiry as the body of the post along with your code.

Hi, Xcode will ask you if you want to install the command line tools the first time you'll try to build something. Or you can do it from within Xcode if memory serves well.

Hi, One thing that your code does not show is what are the base classes of class A and B. If you want to use them as parent of the members variable, they have to from a suitable base classe.

Don't redraw on a resize event but use a QTimer so you repaint only when e.g. the size did not change for 50ms or so.

@KroMignon Indeed!

@lincoln Did you get the way to do it ? Can you share your code if you have done it

@JKSH Here is the output of the debugging it. SocketThread(0x1d02b90b3d0) QThread(0x1d02b870250) QThread(0x1d02b870250) It would see they all have the same id. You don't usually need a thread for a socket. Just leave the socket in the GUI thread. Qt socket classes and other communications classes are asynchronous. i am running a server and i would like to use blocking since that is how i set my sockets up. but i am not sure how you want me to call it if not like i am doing right now.

After a new install from Qt and MinGW it works. Thanks for the help everyone

Thank you all, I'll deal with it !

Thank you all. and The application is responsible for reading the page order and printing accordingly. Not all developers of QT programs are aware of this. Many of them think something like: "My program has no control over the print process. It only calls Qt's print dialog; the rest is done by Qt (and CUPS)." See here: https://github.com/tsujan/FeatherPad/issues/455#issuecomment-731603828

@jsulm , whilst I try to resolve it myself, granted I could also be reading the documentation.

You should reinstall Qt to make sure everything works correctly. Some of the Qt tools - especially qmake - have the installation path baked in. They will not work right away when copied to a different directory. I believe there is a way to fix the paths. However, I cannot remember and I don't know which tools need fixing. To be safe: reinstall Qt in the proper location. It's way easier.

@Ketan__Patel__0011 said in QFuture<void> Thread is not Starting: try to start and stop both function again and again As written in documentation, to start a new function there must be an available thread in the used thread pool: Runs function in a separate thread. The thread is taken from the global QThreadPool. Note that function may not run immediately; function will only be run once a thread becomes available. You could check before starting function how many thread are already used: qDebug() << "Allowed thread:" << pool.maxThreadCount() <<"/ threads in use:" << pool.activeThreadCount() << "/ available threads:" << (pool.maxThreadCount() - pool.activeThreadCount());

The more general term for this is object serialization: translating the object into a well defined format that can be saved to disk or transfered across a network. I'd advise that instead of reinventing and coming up with a custom format. You should review existing formats like XML or JSON, and if appropriate, then acquire or write translators to go between native format and the "serialized" format. Qt already has some serialization capabilities but I don't use them so I'm not sure what specifically exists.

@AnneRanch connect(ui->list, &QListWidget::itemClicked , ui->list_2, &QListWidget::addItem); https://doc.qt.io/qt-5/signalsandslots.html If using overloaded signals see https://stackoverflow.com/questions/16794695/connecting-overloaded-signals-and-slots-in-qt-5

@meganathan If you must call it from a python script, call exit(your_process_exit_code) at the end of the script; passing along the exit code of your process.