Hi again,
I really really hate myself sometimes... Face-palm so hard.
Data* m_data {nullptr};
f->glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA32F,
m_width, m_rows, 0, GL_RGBA, GL_FLOAT, &m_data);
It should be m_data, not &m_data, of course. All is working great now. I will
blam
Hello,
I'm looking for some advices on how to use custom textures with QQuickItems, to
check I'm doing things wrong or not...
I don't know OpenGL very much, I'm just trying to port a python demo code into
a QQuickItem, which uses textures for custom data. Here some of my code:
Textures inheri
On Monday, 27 November 2017 06:05:16 PST Jason H wrote:
> I was wondering what the maximum packet arrival time granularity is for Qt
> (On linux) using a normal timestamp, I can easily do 1ms. However if I was
> dealing with a raw socket descriptor, timing below this there is a ioctl()
> call I can
On 27 Nov 2017, at 16:45, Konrad Rosenbaum wrote:
>
> Yes, the NTP people have done this. Extensively over several decades.
> Please defer to their expertise and use NTP for time sync. ;-)
>
> Using TCP for this purpose is really a bad idea too - because of the built
> in delays and repeat inter
On Mon, November 27, 2017 15:05, Jason H wrote:
> I was wondering what the maximum packet arrival time granularity is for Qt
> (On linux) using a normal timestamp, I can easily do 1ms. However if I was
> dealing with a raw socket descriptor, timing below this there is a ioctl()
> call I can do to g
I was wondering what the maximum packet arrival time granularity is for Qt (On
linux) using a normal timestamp, I can easily do 1ms. However if I was dealing
with a raw socket descriptor, timing below this there is a ioctl() call I can
do to get a lower resolution for the packet arrival time. I'
