General and Desktop

@beginner123 This has nothing to do with qrc. When using qmake, if you set RC_ICONS, qmake creates the rc file in the building folder and adds it to the auto-generated Makefile. But cmake doesn't provide such feature., so you need to create it and add it manually.

Hi,

Non Apple clang is officially unsupported territory. It's also untested.
Xcode is the IDE/Suite of tools but the compiler is clang for quite some time now.

@raven-worx awesome, this pointed me in the right direction. In my case I needed the keyboard combo and key name in string form, so QMetaEnum::fromType was the call I was trying to find, thanks for that.

@zeros0 It works, thanks!

Apparently, there is a nice extension that provides really nice support for all of this:
https://pypi.org/project/PySide6-QtAds/

@Z3PHYR
This attempts to animate/increment a QFont object, which of course makes no sense --- what could it mean/how could it be achieved? You want to animate the font size, which is a number. The types which you can animate are listed in https://doc.qt.io/qt-6/qvariantanimation.html#details.

Have a look at https://stackoverflow.com/a/68131633/489865, and translate to C++. As the guy there says:

There is no property for the font size, though, so there are two possibilities:

create a custom property (by using the pyqtProperty decorator in PyQt);

use a QVariantAnimation, which is not bound to any property;

Pick whichever way you prefer.

If you really want to disable the window setEnabled is the right choice. However, it seems that you don't want to disable the window.

Some widgets allow you to set them to read-only. This might help if the user is not supposed to edit the values while the window is refreshed.

Another thing you might consider is using blockSignals. This means that all changes to the widgets don't trigger any signals. Even your own update does not trigger signals (only bad, if you rely on this).

You could also try to have a model and the widgets just showing the data from the model. Then you have two copies of the model: one for display and one for update. After an update you just swap pointers between these two models (basically double buffering). There is only a very small point in time where you need to synchronize the update and the display.

So @karlphillip on StackOverflow helped me resolve this issue. It turned out the issue had to do with scaling the STL mesh so that it became visible. I had to scale it down to < .01 and there it was.

I hope this helps someone else.

@Paul-Xu
If it works (I would have put it after the QWidget::showEvent(event);) then it's fine, what is not "elegant" about it?

Thanks for your advices, I have already implemented them. Actually, my problem was that all files where not yet created in the remoted folder before I start the scp command.

@abhic
As @SimonSchroeder says, not sure why it should be an issue. But if it really bothers you, don't forget you could delay calling the connect()s/attaching your views to models etc. till the event loop has started by doing them in a function on a QTimer::singleShot(0) which you set off just before the app.exec().

@JonB I'm getting some errors when editing the link🌚 Thanks for the correction.

Hi,

KDE's Konsole also supports Windows, it might be easier to integrate it in your project.

What formats do you get from Qt Multimedia ?

Still cannot post code "Post content was flagged as spam by Akismet.com"

The code in the image gives me

--- 1.1: map true isMapped true isWritable true --- 1.2: map true isMapped false isWritable false --- 2.0: map true isMapped true isWritable false --- 2.1: map false isMapped true isWritable false --- 2:2 map false isMapped false isWritable false

Without any sleep() it does indeed work, but I mean in reality there is some delay between frames in a video, right? I feel there is a bug somewhere.

Screenshot 2024-11-17 191040.png

@JonB Nothing to do with QSettings. It was a Unix locale issue. It turns out that the QSettings stuff was left there by the original developer of that code to allow testing without switching the language of his system. It mightily confused me ...

Hi @Zeshan, at first you should clarify if you want to use Modbus TCP or MQTT, as these are two completely different protocols.

Regards