General and Desktop

@lansing Yep. For "most" cases, you can just just use (...) and pick out the desired capture(s). I don't know what you were looking at in SO, but suffice to say that the need for "lookahead" or "lookbehind" assertions is "unusual", unless you have a specific need.

@nickqu Take a look at https://doc.qt.io/qt-5/qttestlib-tutorial3-example.html

@SPlatten #include <QCursor> ?

@SPlatten I think it should be inline QString id() const { return faultID().toString() + m_location; } inline QUuid faultID() const { return m_faultID; }

@Perdrix said in Examples of all built-in Styles: PS Is there a "Dark Theme" version of Fusion or similar? Nope. However, you can make a basic one with palette https://stackoverflow.com/questions/15035767/is-the-qt-5-dark-fusion-theme-available-for-windows

@chihwah Well, I just learned from googling and practicing. I used to have a lot of third-party libraries building work...

I don't think it is a good idea trying to implement this behaviour. It is good that you think about your users accidentally deleting something. However, I have not encountered this problem. The major point not to implement this is because it is unexpected behaviour. No software does this and it is more likely a point for user frustration instead of helping them. Maybe they have switched to another program shortly, e.g. a chat or similar. Your window is still (partially) visible and they want to get quickly back to work. So, they might be clicking your button on purpose, but nothing happens. They become frustrated because their (maybe fast) computer is too busy to register the click (at least in their perception). After a few seconds they notice that actually nothing happened and they click again. If this only happens for some of your application's buttons it is even more confusing. Maybe they actually figure out that clicking buttons in your application when it wasn't in focus requires two clicks. But, you haven't implemented it for all your buttons. Then the user clicks one of the buttons which does not support this behaviour twice as they have learned it. Suddenly, they have triggered the action twice. You cannot expect any user (other than yourself) to understand this. The potential problems I described above are magnified when someone has a multi-monitor setup with your app fullscreen on one of them. Try to stick to user interface guidelines to not annoy your users. I believe that users are trained to subconciously not click on buttons to bring an application back into focus.

@Beoo said in Problemes with the online installer: Did i need to make an Text file Called qt5vars.cmd and the content of Yes "can i set as CALL C:....\Visual Studio\2019...\vcvarsall.bat from the community Version" - yes "and what had i to do to create the the link?" - right click on desktop, new -> shortcut "Is there a way to crosscompile from Ubuntu for Windows?" - in theory, but I would not do that The problem with online installer is known and unfortunately still not fixed. It is not the installer itself, but slow/broken mirrors. You could also try again later.

@takti You need to understand that most people in this forum are volunteers spending their own time to help others for free. This includes me as well. Since I don't have a solution for your problem I suggested to check somewhere else also.

@Tom-asso said in Can my app provide resources loaded by a Qt library?: And if the library code also specifies an "alias" for the resource, there is still no way around the absolute path? Nope. An alias is still a hard-coded path as it cannot be changed at runtime.

Looks like https://bugreports.qt.io/browse/QTBUG-75210 is relevant here.

@asad-ali thanks for your effort ;)

Good then please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found.

@usman-qt We would like to share with you that QT support has been added to the Aspose.PDF for C++ 20.6. We have created and successfully tested QT project that used Aspose.PDF for C++.

Glad you found out and thanks for the detailed solution !

If timer2 timeout value is greater than timer they will be in order: function -> timerTimeoutSlot -> timer2TimeoutSlot.

@stretchthebits If you only want to totally turn off the auto-exclusivity, you can simply call setAutoExclusive(false) to every button. I think there's no need to useQButtonGroup in that case.

@Qwerty123098 No this is not possible. Just the array without adding your special characters. (A-Z,a-z,0-9)

@VRonin Thanks, a written example is a lot easier to understand. I was going through the Qt documentation over and over and couldn't find an good example for this.