General and Desktop

AP units are not required to broadcast the SSID. It's often not broadcast, as a security measure.

@SGaist Sorry, my non-response to @JoeCFD made it seem like I didn't do that. My apologies for that. Now, although I am not getting the "not found" error, the app will not build. I will post a new post to the forum in a little while, as it is an entirely different issue now. Thank you all for your help.

Hi and welcome to devnet, You need to create a subclass of QStyledItemDelegate. All Qt views inherit from QAbstractItemView.

Possible but I don't know them all.

@Christian-Ehrlicher Thanks! Silly mistake, I will continue to tune

Just a note about a non-Valgrind, windows-specific leak-checking method: https://docs.microsoft.com/en-us/visualstudio/debugger/finding-memory-leaks-using-the-crt-library?view=vs-2019 It has been a while since I have done any extensive work on a Microsoft platform, but in my recollection crtdbg.h can do many helpful diagnostic things, although it is sometimes tricky to get all the debug build settings configured in the way that will trigger the features you seek.

@CuriousPan said in How to create Resources folder?: Resources = nameOfApplication.qrc the pro-file is case-sensitive

changed to Matlab --> https://github.com/Christoph-Lauer/Transfer-Function-Extractor-Matlab

@JonB Hi, thank you for your answer. I am going to go with the final way that you mentioned. That is cblist = self.findChildren(QCheckBox) for cb in cblist: cb.setEnabled(True) That worked for me. Thank you very much, I appreciate it.

@jsulm Yes, it should work well too. Thanks.

@jsulm You were right! It's solved! Thank you, but why is the layout broken after clicking Print? [image: 9a329d7d-eb5b-49c0-9cbd-957d86081767.png] [image: 5e70faff-b2b8-4637-80a4-eb8d27f82dbe.png]

@eyllanesc thank you for the solution

If wmaster is a factory and wlogin inherits it this also makes wlogin a factory. That doesn't sound right that wlogin should be a factory. Honestly, I am not an expert on many of the design patterns, so you try to read up on the things I mention. However, to me a factory class usually only has static method: You don't need a factory object and you can just call the methods to create new objects (like the QLabel). This also means that you are right that a factory should be a component and not a superclass. BTW, to make a factory a class also comes from pure OOP (like is required from Java). But, you don't actually need an object here and just want to call methods that do something. Since C++ is multiparadigm, to me personally a better approach would be to use free standing functions instead of methods for the factory. These can then be put into a namespace to clean things up a little.

@LISP said in How to implement TCP communication with QT: Is it better to use a separate thread in the client program as well? Only if really needed. Qt is assynchronous, so usually there is no need for additional threads. You only need threads if the main thread becomes too busy. But that is something you need to know or to test. How many connections do you want to maintain at the same time? If client has only one connection there is absolutelly no need for any threads.

Have you done it? Can you share it

@Bruce-Zhang Did you enable C++17 in your pro file? CONFIG += c++17