Qt 6

I have the same problem, did you find the solution ?

Hello, I also miss FTP since I switched to Qt 6. I don't like the idea of using libcurl because the more dependencies is added to an application, the more potential problems + the harder is the maintenance. I really hope that Qt will but back FTP support.

It seems I found a reson for that

on Windows apart of the screen resolution it's possible to adjust the size of text, apps etc.
This was set on 125% on the desktop from with I tried. After setting to 100%
result is
PyQt6.QtCore.QRect(0, 0, 2560, 1440) as needed

This is definitiv a different behavior between pyqt 6 and 5

@Antonius said in Future of Qt module xmlpatterns?:

for letting us know that we are "no one".

Feel free to take over the maintainance for this module...

And if you're a paying customer you can ask TQtC if they will port it for you.

the solution to this problem is most probably to enable harfbuzz, cf https://stackoverflow.com/questions/73256254/static-qt-build-messes-up-text
When using conan recipe this is done by setting option qt:with_harfbuzz=True

Hi and welcome to devnet,

Just keep using cmake.

Here for Qt 5

Here for Qt 6

I created task on bug tracker.
On other versions (6.2.2, 6.3.2) works fine

https://bugreports.qt.io/browse/QTBUG-106750

@Asperamanca said in mapToGlobal, wrong values with Linux:

Yup that looks like it.

I don't get why someone thought it's a smart move to do it this way

One advantage is that there's a clear separation between both builds in the configure system. In the Qt 5 one, some options applied to the host tools, some to the target tools and binaries, and some to both.

May I ask what is the specific command, I also encountered this problem, and still can't solve it.

Once I installed/updated libicu-50.2-4.el7_7 that updated libicu-devel-50.1.2-15 and lo and behold the make completed and installed.

I scoured through the source code more and found out that there is apparently currently no support to play from a QIODevice, only from either a network url, a qrc-baked file or a local file. I eventually resorted to writing QIODevice output to localhost port as UDP packages and read the videostream from there, data happened to already be in mpeg-ts format.

Still no idea how the mention of adding mime type information would work, but it's now obsolete need for my project.

i was able to solve it with instantiating a QVideoSink and setting that as the output, and hooking into the videoFrameChanged signal. i keep a list of the videoSinks i want to send the frames to, and farm them out when i get the videoFrameChanged notify

@jsulm Ok I'll do. Thx for the advice.

I did get all of these issues solved yes.
1: create a new subclass of QtAbstractVideoSurface, and override the present() function to do your multiplexing, set your subclass as the one video sink
2: instead of hooking into QAbstractVideoSurface::surfaceFormatChanged, hook into QMediaPlayer::metaDataChanged
3: i guess you don't need it if you do the above?

@A-N-E HI Im new. But I had this same issue. The way I corrected this was I made sure to correct the code inside the converted .PY file. Somewhere in the code was my import resource. Once I converted my resource file, I made sure that the .PY file knew I made that change as well. Sure enough, it fixed the issue I was having! Hope this helps you!