qRgb() and qRgba() only exist for (A)RGB, though, and I don't have an issue
with RGB32 which works as I would expect.
Otherwise, a function that would put the bytes where it wants would be great.
It's just the BGR(A) that doesn't work as documented regardless of whether you
treat it as an unsigne
Maybe you should use qRgb() or qRgba(...) and let it put the bytes where it wants? also, note that there are qRed(), qBlue(), qGeen(), and qAlpha() which should take care of extracting the aproproate channel for you.
If you told me that in Qt, BGR32 (and BGRA32) is 0xAABBGGRR, I would agree.
On Thursday, 14 November 2019 21:37:09 CET Allan Sandfeld Jensen wrote:
> On Thursday, 14 November 2019 21:17:38 CET Stefan Fabian wrote:
> > That may be explained by the endianness, though, since ARGB as 32bit uint
> > on little-endian (what most if not all consumer pcs use) would be BGRA in
> > m
On Thursday, 14 November 2019 21:17:38 CET Stefan Fabian wrote:
> That may be explained by the endianness, though, since ARGB as 32bit uint on
> little-endian (what most if not all consumer pcs use) would be BGRA in
> memory. In the case of BGRA32, endianness could change it to ARGB but not
> ABGR
That may be explained by the endianness, though, since ARGB as 32bit uint on
little-endian (what most if not all consumer pcs use) would be BGRA in memory.
In the case of BGRA32, endianness could change it to ARGB but not ABGR or RGBA
as in my test.
Either way, it should be documented how raw mem
I had a similar finding.
i find that QImage::Format_ARGB32 is always 0xBBGGRRAA on both mac and windows
unrelated to video, but just allocating a QImage
> On Nov 14, 2019, at 11:54 AM, Stefan Fabian
> wrote:
>
> Hey guys,
>
> I'm interfacing external camera input to Qt/QML (version 5.9.5 on
Hey guys,
I'm interfacing external camera input to Qt/QML (version 5.9.5 on Ubuntu 18.04).
For this, I'm using a custom video source and present the frames using
QVideoFrame and QAbstractVideoBuffer.
The image is displayed in QML using a VideoOutput.
Since not all formats can be mapped directly,
So there's a couple ways in iOS to get the SSID. But I was hoping, since I need
to target android as well, that I can have a Qt solution that "just works"
complete with SSID change monitoring. There's two APIs: NEHotspotHelper which
requires and entitlement or CaptiveNetwork which was deprecated
