On domingo, 6 de maio de 2018 05:24:07 PDT Jason H wrote:
> I was surprised to learn that QBluetoothSocket is not derived from
> QAbstractSocket? This caused meet to write nore code than I feel I should
> have. QBluetoothSocket does derive from QIODevice at least so reading and
> writing is not aff
On sábado, 5 de maio de 2018 07:58:45 PDT Roland Hughes wrote:
> While all of this is an entertaining conversation, it doesn't change the
> fact that big-endian ___must___ remain the default binary format for the
> class in question. That class was initially created for the sole purpose
> of commun
On sábado, 5 de maio de 2018 07:58:45 PDT Roland Hughes wrote:
> Data centers have been moving to ARM (the new absolute bottom) and
> Z-machines for quite some time now.
And yet they represent less than 0.1% of the market share.
> The x86 has both heat and power problems which cannot be overcome.
It's weired that the same code on another pc (same qt version, but win10x64
professional) works fine. as the widget recevied these keys, so it seems
impossible that it's due to some global hot-keys.
At 2018-05-04 08:55:09, "nus1998" wrote:
Hi All,
I have some questions on keyPressEvent o
I was surprised to learn that QBluetoothSocket is not derived from
QAbstractSocket? This caused meet to write nore code than I feel I should have.
QBluetoothSocket does derive from QIODevice at least so reading and writing is
not affected. It seemed that because Bluetooth is a "service" that the
